Browse documentation
Help
Troubleshooting
Resolve common setup, monitoring, invitation, and notification problems.
A monitor is down unexpectedly
- Open the site detail and inspect the latest status code, response time, and failure evidence.
- Confirm the monitored URL is public and responds without an interactive login.
- Check that the expected status matches the endpoint's real response, including redirects.
- Increase the timeout only when the endpoint is expected to respond slowly; the allowed range is 5 to 60 seconds.
- Use pause during planned maintenance, then remember to resume monitoring.
Alerts are not arriving
- Confirm the integration exists and is enabled for the active team.
- Open the site Alert settings and confirm the destination is selected for the missing event type.
- For slow-response alerts, confirm the feature is enabled and the threshold is appropriate.
- Rotate and replace revoked Slack or Discord webhooks and expired external credentials.
- Check spam, channel permissions, bot membership, and recipient identifiers in the destination service.
A teammate cannot access the team
- Confirm the invitation is still pending and has not expired or been revoked.
- Make sure the teammate signs in with the exact invited email address.
- After acceptance, use the team switcher to select the new team.
- If an action is unavailable, compare the member's role with the roles and permissions guide.
Still need help? Contact support@downbot.pro.Get support