Issues are team-scoped incident records created when automatic monitoring crosses your configured thresholds. They group repeated failures for the same site and check tool so you can triage problems without an alert for every individual check.
Manual checks save results to check history and can send completion notifications, but they do not open or resolve issues.
When issues are created
SitePulse opens an issue when an automatic check meets the problem thresholds configured under Monitoring and the check tool has issue opening enabled for that team or site. Examples include:
- Repeated status failures after confirmation retries
- Invalid or expiring SSL certificates
- DNS hard failures or missing expected records
- Broken-link counts above your threshold across consecutive crawls (after team or site link filters are applied)
- Performance scores, TTFB, or load time (TTI) outside configured limits
When the underlying problem clears on subsequent automatic checks, SitePulse marks the issue resolved and can send recovery notifications.
See Monitoring settings for the full threshold reference.
Issue lifecycle
| Status | Description |
|---|
open | Active incident that needs attention |
acknowledged | Someone on the team is investigating; recorded with the acting user and timestamp |
resolved | The problem has cleared; kept for history |
fingerprint field deduplicates incidents so a recurring problem updates one record instead of creating many.
Issues page
Use Issues to filter, sort, and act on incidents for the current team.
Available filters:
- Status — Active, Open, Acknowledged, or Resolved
- Site — one site or all sites
- Tool — Status, SSL, DNS, Broken Links, Performance, or all tools
- Severity — Critical, Warning, Info, or all severities
You can sort by summary, site, tool, status, or opened date. Issue summaries link to the related check result when SitePulse has one.
Actions
Select one or more issues to use bulk actions.
| Action | Available when | Effect |
|---|
| Acknowledge | Selected open issues can be acknowledged | Marks them as acknowledged and records who acted |
| Resolve | Selected active issues can be resolved | Marks them as resolved manually |
| Delete | Selected issues can be deleted | Removes the incident record from the dashboard |
Broken-link entries appear on the Issues page only after the site breaches its broken-link issue rule. A latest broken-link check with one failed URL may show on the Sites page without opening an issue if it is below your threshold.
Severities
| Severity | Typical use |
|---|
critical | Site down, invalid SSL, DNS hard failures |
warning | Expiring certificates, broken-link thresholds, performance breaches |
info | Lower-priority signals when configured |
Notifications and quiet time
Issue lifecycle events drive outbound alerts:
- Issue detected — when a new issue opens (including when a resolved issue reopens)
- Issue resolved — when automatic monitoring confirms recovery
- Escalation — follow-up reminders while an issue stays open or acknowledged (when escalation is enabled)
Configure destinations under Notifications. Quiet time (set in Monitoring) suppresses outbound alerts but does not stop checks or issue evaluation.
See Notifications for channel setup and Webhook notifications for HTTP payload and delivery details.
Site-level controls
Per-site settings can affect issue behavior:
- Snooze — pauses issue opening until a datetime passes
- Threshold overrides — different problem rules for one site
- Enabled issue tools — disable issue opening per tool while checks still run
- Disabled check tools — if a tool is not enabled on the site, it is not checked or evaluated
See Managing sites for override options.
API access
Integrations can read issues through the v1 API with the issues:read scope. The API is read-only — acknowledge and resolve actions are available in the dashboard only.
See Issues endpoints and the Issue resource. 
