Modify information
After an incident triggers, its symptoms may become clearer over time. You can modify key information like the incident title to make it more accurate than the original alert information.- Modify Incident Title
- Modify Incident Severity
- Modify Incident Description and Impact
1
Open Incident Details
Click to open incident details in console, in the title section, click the edit button.
2
Enter New Title
Enter the new title, done.
The modified title won’t change when new alerts merge in.
Acknowledge incident
You have three ways to acknowledge a newly triggered incident.- Acknowledge via Console
- Acknowledge via IM App
- Acknowledge via Voice Call
- Acknowledge via Flashduty App
- Single Acknowledge: Click incident details in console, click Acknowledge button to complete
- Batch Operation: In console incident list, select multiple triggered incidents, click Acknowledge button for batch acknowledgment
If an authorized account member has configured an acknowledgment custom form and the current incident meets its visibility conditions, clicking Acknowledge first opens that form. Otherwise, Flashduty acknowledges the incident directly. See Custom Forms.
Unacknowledge incident
Once anyone acknowledges, incident progress changes from “Triggered” to “Processing”. Others acknowledging won’t change the progress. After acknowledging, you can choose to Unacknowledge, useful for accidental acknowledgments. When all acknowledged personnel unacknowledge, incident reverts to Triggered status.Progress and MTTA
You can view each person’s assignment time and acknowledgment time in the console. We calculate incident MTTA as follows:Snooze
After acknowledging an incident, responders may need time to investigate and handle it. Snooze can temporarily stop the incident from escalating per the expected escalation rule. After acknowledging, you can choose from preset durations (default: 2 hours, 4 hours, 12 hours) or set a custom duration (hours or minutes, up to 30 days).- Snooze via Console
- Snooze via IM App
- Snooze via Flashduty App
Click incident details in console, click More (⋮) in the top-right, choose the Snooze submenu, select snooze duration, done. Only incidents in the Processing state can be snoozed.
Close incident
You can close an incident in any status. Closing sets its progress to Closed, and its alerts stop merging new events. If an alert hasn’t recovered in the original monitoring system, later events will trigger new alerts and incidents in Flashduty On-call.- Close via Console
- Close via IM App
- Close via Flashduty App
- Single Close: Click incident details in console, click Close button to complete
- Batch Operation: In console incident list, select multiple triggered incidents, click Close button for batch closure
If an authorized account member has configured a close custom form and the current incident meets its visibility conditions, clicking Close first opens that form. Otherwise, Flashduty closes the incident directly. See Custom Forms.
Reopen incident
If you closed an incident by mistake, reopen it:1
Initiate reopen
In the closed incident details page, click the Reopen button.
2
Enter reopen reason
In the dialog that appears, enter the reason for reopening. This field is required and records why you reopened it.
3
Confirm and submit
Click Save to complete. The incident reverts to Triggered status and re-initiates assignment and notification.
The reopen operation supports batch operations. You can select multiple closed incidents in the incident list and reopen them together.
More actions
The More button at the top right of the incident details page groups supplementary actions beyond the high-frequency action buttons. The visible items are rendered dynamically based on the incident’s progress and acknowledgment state.Merge
You can manually merge between incidents, or between incidents and alerts. Merging similar alerts and incidents together consolidates information into the same incident, accelerating the handling process.Merging changes which incident an alert belongs to. If all alerts of an incident are merged into others, that incident closes automatically and you only need to handle the target incident. The timeline records every merge.
FAQ
I snoozed an incident, why does the system still trigger new similar incidents?
I snoozed an incident, why does the system still trigger new similar incidents?
You may have confused Snooze with Silence, they’re quite different.
If you need to suppress an alert policy, use Silence, not Snooze.