Resolving Issues
How to resolve status page issues and restore operational status.
Resolving an issue returns the affected component to operational status. Issues can be resolved through Chat or automatically when linked alerts are resolved.
Resolution methods
Issues can be resolved through Chat or automatically when linked alerts are resolved.
Using Chat
Ask Chat to resolve an issue:
"Resolve the checkout service outage issue"
The assistant will mark the issue as resolved and update the component status to operational.
Via alert resolution
If the issue was created from an alert, resolving the alert automatically resolves the linked issue. See Auto-resolution below.
Auto-resolution
Issues linked to alerts are automatically resolved when the alert is resolved.
How it works
When you resolve an alert that has an associated status issue:
- The alert moves to resolved state
- The linked issue is automatically resolved
- The component status updates to operational
- Both timestamps are synchronized
Keeping status in sync
Auto-resolution ensures your status page stays accurate without manual intervention. When you resolve an alert:
- From the dashboard
- From Slack inline actions
- Via the API
The linked status issue resolves automatically.
Auto-resolution only applies to issues created from alerts. Issues created directly by Chat during investigations must be resolved manually or by resolving the associated alert if one exists.
Resolution timing
Choose when to resolve issues carefully to maintain accurate status history.
When to resolve
Resolve an issue when:
- The underlying problem has been fixed
- The component is fully operational
- Users are no longer experiencing impact
When not to resolve
Do not resolve prematurely:
- When symptoms have stopped but the root cause is unfixed
- During temporary recovery that may regress
- While monitoring to confirm stability
Impact on uptime
Resolution timing affects your uptime calculations:
- Issue duration = resolvedAt - startedAt
- Uptime percentage uses total issue duration
- Premature resolution followed by new issues creates multiple entries
Issue history
Resolved issues remain accessible in your status page history.
Visibility
After resolution:
- Issue appears in the resolved issues list
- Shows in the component timeline
- Contributes to historical uptime data
Duration calculation
Each issue's duration is calculated and displayed:
- Short format for recent issues (e.g., "23 minutes")
- Full timestamp range for historical review
- Used in uptime percentage calculations
Reporting
Resolved issues are available for:
- Post-mortem reviews
- Uptime reporting
- Trend analysis
- Compliance documentation