Bulk action permissions and limits
This article lists who can apply each bulk action, the limits that apply, and what each message in the bulk actions bar means.
Permissions
Oppex checks each selected incident separately against the rules below.
| Status | Who can apply it to an incident |
|---|---|
| Acknowledged | The person the incident is assigned to, or anyone who belongs to the escalation policy that the incident was routed to. This rule is the same for every role. |
| Snoozed | Only the person the incident is currently assigned to. This rule is the same for every role, including Owners and admins. |
| Resolved | The person the incident is assigned to, whatever their role. Owner, Global Admin, and Workspace Admin: any incident. Admin: incidents on services they are an admin of, or whose escalation policy they belong to. Responder: incidents on services whose escalation policy they belong to. |
An incident shows no checkbox when you cannot apply any of the three statuses to it.
Limits
| Rule | Detail |
|---|---|
| Statuses available in bulk | Acknowledged, Snoozed, and Resolved |
| Selection scope | Individual incidents, every incident on the current page, or every incident that matches your current filters |
| Incidents already in the target status | Skipped without error |
| Snooze duration | One value for the whole selection. Minimum 1 minute. Maximum is your workspace setting, 24 hours by default. |
| Snooze notifications | None are sent |
| Resolve notifications | Not sent for incidents created more than 30 days ago |
| RCA on bulk resolve | When your workspace requires an RCA, the RCA you submit is copied to every selected incident |
| Undo | Not available |
Messages in the bulk actions bar
When you choose a status, Oppex checks whether you can apply it to each selected incident. If you cannot apply it to some of them, a yellow note appears under the bar. The note ends with the rule that applies to you.
1 incident was deselected. You can only snooze incidents assigned to you.
✓
● Triggered
High CPU usage on payments-api
✓
● Triggered
Database connection pool exhausted
Disk usage above 90% on payments-db
| Message | Meaning | What to do |
|---|---|---|
| "N incidents were deselected." | You cannot apply the chosen status to those incidents, so Oppex unticked them and greyed out their checkboxes. | Continue if the remaining selection is correct. If you choose a different status, Oppex re-ticks the incidents that can take it. |
| "None of the N incidents you picked can be snoozed." | You cannot apply the chosen status to any incident you selected. Apply is disabled. | Choose a different status, or select other incidents. |
| "Checking which of the selected incidents you can resolve…" | You selected all incidents across all pages, and Oppex is checking each matching incident. | Wait a moment. The note changes to one of the messages below, or disappears if nothing will be skipped. |
| "X of N incidents will be skipped when you apply." | You selected all pages, and you cannot apply the chosen status to X of the matching incidents. | Click Apply to update the rest, or narrow your filters first. |
| "None of the selected incidents can be resolved." | You selected all pages, and you cannot apply the chosen status to any matching incident. Apply is disabled. | Choose a different status, or change your filters. |
| "Incidents you can't resolve, if any, will be skipped when you apply." | You selected all pages, but Oppex could not finish checking the matching incidents. | Click Apply. Oppex tells you afterwards how many incidents it skipped, if any. |
The status in each message matches the one you chose. When your role lets you apply the status to every incident (for example, an Owner resolving), no note appears.