How can we help?

If an automation or scheduled workflow did not run when expected, begin by checking its configuration and execution history. A missing result can indicate several different situations: the automation was not triggered, execution started but failed, or execution completed without producing the outcome you expected. Troubleshooting steps 1. Verify the automation is enabled. Check whether the relevant automation or workflow is active and configured for execution. 2. Review the trigger. Confirm that the triggering event or scheduled condition was actually satisfied. For event-based automations, check whether the expected event occurred. For scheduled operations, review the configured date, time, recurrence, and timezone. 3. Check the execution history. Look for an execution corresponding to the expected trigger. If an execution exists, inspect its status and any available error information. 4. Review dependencies. If the workflow depends on another operation, external integration, or required input, verify that the dependency was available. 5. Check permissions. Confirm that the configured operation has the necessary authorization to access its required resources. 6. Review recent configuration changes. A modification to the trigger, workflow steps, integration, or permissions may explain why the behavior changed. 7. Verify the expected output. Some workflows may execute successfully without creating a visible result if their conditions do not require further action. What if there is no execution record? This may indicate that the trigger did not occur or that execution did not begin as expected. Check the scheduling and triggering conditions before changing the workflow. What if the execution failed? Review the recorded error and identify the failing step. Correct the underlying problem before retrying. Can I run the automation manually? Where manual execution is supported, it can help test the workflow. However, review the potential effects before starting a manual run, particularly if the workflow sends messages, updates customer records, or performs financial or operational actions. When to contact Support Include the automation name, expected execution time, timezone, configured trigger, observed status, and any available execution identifier.