Each automation run keeps its own output. Use the automation's History to inspect what happened, rather than inferring success from its enabled state or the time on the schedule.
Review a run
- Open the automation.
- Open History and select a run.
- Check its state and open the associated conversation.
- Review the output, tool results, and any requests for input.
A run can be pending, running, completed, or cancelled. Read the conversation when the result is incomplete or an external action failed; a status label alone does not explain the outcome.
Pause or resume
Use Pause to stop future automatic starts, and Enable when it should run again. Pausing future starts does not undo completed actions or necessarily interrupt work already running. Open an active run's conversation to inspect it and use the available stop control if you need to interrupt that work.
Diagnose a missing run
Check the enabled state, next scheduled time and timezone, or the event's matching conditions. For account-backed triggers, check the connection in Plugins. For a run that started but could not finish, inspect missing source access, unavailable models, or required input in the conversation.
After fixing the cause, review whether it is appropriate to retry. Check the destination service before repeating actions that send messages or create records.