Use a Sim Workspace Events trigger to run an alert workflow when another workflow fails, slows down, exceeds a cost threshold, or goes quiet. Add delivery blocks for the channel you use, such as Slack, email, or an incident API.
Example: notify Slack after repeated failures
- Create a workflow with Sim Workspace Events as its trigger.
- Set Event to Consecutive Failures and Consecutive Failures to
3. - Select the source Workflows. Leave the field empty to watch the workspace.
- Add a Slack block that sends a message to your incident channel. Choose the intended Slack account and channel.
- Include the trigger's
workflowNameandtriggeringRun.runIdin the message using the reference picker. For a trigger namedworkspaceevent, the message can be:
Workflow <workspaceevent.workflowName> has failed repeatedly.
Latest run: <workspaceevent.triggeringRun.runId>- Deploy the alert workflow to activate it. Trigger representative failures in a watched test workflow, then inspect the alert workflow's run log and the Slack message.
Choose another condition
Choose Run Error to respond to each failed run. Other conditions include failure rate, error count, latency, cost, and inactivity. Cost thresholds use credits. See the event and rule reference for settings, defaults, and event-specific outputs.
Rule-based subscriptions have a one-hour cooldown after firing; plain events such as Run Error do not. Rate-based rules need at least five runs in their window. A subscription does not receive events about its own workflow, and runs started by this trigger do not emit new workspace events.
Delivery behavior comes from the action blocks you configure. If an alert is missing, check that the alert workflow is deployed, the source workflow matches its filter, the condition and cooldown allow it to fire, and the delivery block completed successfully.