Occurrences and responses

An occurrence is one concrete execution of a rule. It owns its delivery attempts, provider receipts, response capability, and terminal state.

Available actions

• Acknowledge confirms that you saw the notification.
• Complete records that the requested work is finished.
• Snooze moves the next delivery to a later time.
• Skip closes the occurrence without completing it.
• Cancel administratively stops an active occurrence from the authenticated app or API.

The actions shown depend on the rule and current state. Repeating an already-applied action is safe and returns the resulting state.

Secure response links

Pushover links contain the secret response token in the URL fragment. Browsers do not send that fragment in the initial HTTP request. The response page keeps the token in memory and sends it only in the dedicated Anchor response-token header.

Expired or invalid links do not reveal occurrence details. A terminal link can show the final state without reopening the occurrence.