> ## Documentation Index
> Fetch the complete documentation index at: https://doc.entelligence.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Automation permissions and troubleshooting

> Govern automation context, Slack permissions, matching, duplicates, schedules, retries, external actions, and troubleshooting.

Every automation needs a clear trigger, instruction, context boundary, destination, owner, and rollback.

## Common problems

| Symptom                          | Check                                                                 |
| -------------------------------- | --------------------------------------------------------------------- |
| Pulse does not run               | Active state, schedule, timezone, and next occurrence                 |
| Trigger Now sends nothing        | Slack connection, recipient mapping, and channel membership           |
| Report reaches wrong user        | Manager selection and Slack user mapping                              |
| Duplicate report                 | Overlapping Pulses, retry behavior, or a manual trigger near schedule |
| Reactor ignores a message        | Channel, required keywords, allowed user IDs, and active state        |
| Reactor runs too often           | Narrow inclusion rules and add exclusions                             |
| Reactor runs on excluded message | Exact skipped keyword/user ID and saved configuration                 |
| Answer lacks context             | Connector health, source permissions, and instruction scope           |
| External action fails            | Connector write permission, destination, and required fields          |
| Paused automation still appears  | Pause stops execution; it does not delete the row                     |

## 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](/automations/pulse) or [Reactors](/automations/reactors) after correcting the trigger or permission.