Team operations
Review automation history
Distinguish a rule that never started from a skipped or failed run.
Before you start
This guide covers Operations automations. Instagram rules are reviewed through Manage in Nod AI.
Step by step
- Open Automations and select History.
- Find the rule name and date of the run you want to investigate.
- Read its status and detail: completed, skipped, and failed mean different things.
- For a skipped run, compare the event with the rule’s conditions.
- For a failure, review the indicated action, its data, and its required integration.
- Return to the rule to fix its configuration, then verify an authorized execution.
What to include when asking for help
Record the rule name, date, status, and error detail. Explain what you expected and which record was involved, without keys or unnecessary private information.
History records what happened; it does not guarantee automatic retries. Fix the cause before testing again. For email or access actions, confirm the outcome with the relevant recipient or client.
What to expect
You can identify whether to review the trigger, a condition, or a particular action.
Troubleshooting
Without a run, check whether the rule was active and its trigger occurred. Saving a draft does not generate an event by itself.
Do not repeat an operation with real effects without checking completed actions; you could duplicate a notification or delivery.