Skip to main content
Every automation needs a clear trigger, instruction, context boundary, destination, owner, and rollback.

​
Common problems

​
Governance checklist

  • Use a named workspace owner.
  • Start in a non-production channel.
  • Keep instructions in change control.
  • Test positive and negative cases.
  • Avoid secrets in instructions or Slack events.
  • Prefer draft or read-only actions.
  • Confirm how retries and duplicate prevention work for your workspace.
  • Confirm required audit history before a regulated rollout.
  • Pause immediately when behavior is unexpected.

​
Delete versus pause

Pause while tuning or investigating. Delete only after checking that no team, channel, report, or runbook depends on the automation. Record the instruction and schedule if recreation may be required.

​
Support details

Include automation name and type, workspace, Slack channel or recipient, schedule and timezone, triggering message timestamp, matching rules, expected action, actual result, and redacted error.

​
Next step

Return to Pulse or Reactors after correcting the trigger or permission.