Why didn't my automation run?

When an automation does not run as expected, the event and run history can show exactly where the process stopped. This guide walks you through the checks in order, from confirming that HireData received the event to inspecting an individual automation step and safely testing your correction.

​

First identify where the process stopped

Before changing the automation, check how far the event progressed. This helps you focus on the relevant settings.

​

1. Confirm that HireData received the event

Every event-based automation starts with information received from a connected app. If the expected event is not in HireData, the automation has nothing to process.

1. Select Events in the main navigation.
2. Search for the candidate, contact, or event you expected to start the automation.
3. Open the event.
4. Check the Data tab to confirm that the expected fields and values are present.
5. Use the code view (</>) when you need to inspect the raw JSON or confirm an exact field name.

If you cannot find the event, check whether the change was saved in the source app and whether its HireData connection is working. For Carerix connection problems, see Why is my Carerix not syncing with HireData?. For more information about the event detail view, see Events.

​

2. Check whether the automation is active

An inactive automation does not create new runs when matching events arrive. Open the automation and look at the action in the upper-right corner:

• Pause means the automation is currently active.
• Activate means the automation is currently inactive. Select Activate when you are ready for new events to enter it.

​

3. Compare the event with the Start configuration

If the event exists but no run was created, compare the event with the automation’s Start block. The app, trigger, and conditions must match the incoming event. Check for:

• A different app or object from the one that produced the event
• A different trigger, such as Created instead of Updated
• A required field that is missing from the event
• A field value that does not satisfy one of the Start conditions
• A field whose name, type, or format changed in the source app

Use the event’s Data tab while reviewing the Start block so that you can compare the actual values rather than the source record’s current values. If you change the Start configuration, save the automation before testing it again.

​

4. Inspect the run and its steps

If a run exists, the automation did start. The run timeline shows how the event moved through the automation and where it stopped.

1. Select Runs in the main navigation.
2. Find the relevant run and select its row.
3. Select the step that stopped, failed, or was cancelled.
4. Review the step’s Overview, Fields, and Related tabs.

The Overview tab can contain the result or cancellation message. Fields shows the values used or produced by the step, while Related links the run back to its automation and event. For explanations of common cancellation messages, see Run Cancellation Reasons. For more information about reading a run, see Runs.

​

5. Test the correction

Once you have found and corrected the cause, test the automation again. A new event is the safest option because it creates a fresh run without repeating actions from the earlier one. If creating a new event is not practical, you can replay the original event:

1. Return to the event.
2. Open its Runs tab and review what already completed.
3. Select Replay.
4. Open the new run and confirm that it follows the expected path.

​

Need more help?

If the automation still does not run as expected, contact support@hiredata.com. Include:

• A link or the ID of the event
• The automation name
• The run ID, if one was created
• The result you expected
• The step or condition where the process appears to stop
• The exact cancellation or error message, if one appears