> ## Documentation Index > Fetch the complete documentation index at: https://help.hiredata.com/llms.txt > Use this file to discover all available pages before exploring further. # Events > Learn how events work in HireData: how connected apps send them, where to find the event log, and how to inspect payloads to debug your automations. *When you connect your ATS, such as Carerix, Salesforce, OTYS, etc., to HireData, it will start sending events, which are notifications that something has happened in your system. Events trigger your automations, making them crucial to how HireData works in the background. In this article, we'll explain how events work, where to find them, and how to analyse them if something doesn't go as expected.* ## What is an event An event is a signal sent from your connected app to HireData. It usually represents a specific action or change, for example, a new candidate being created, a vacancy being updated, a placement being completed, etc. These events are used to trigger the automations you've set up in HireData, and every event includes **Event Data**, **External Records **and** Processes.** *Event example:* Individual event page ## How to view event details Navigate to the **Settings** menu and open the **Events** page to see a list of all events sent from your connected apps: Events page in HireData *Use the filters for a more organised view, for example, if you want to see the events coming from one of your apps:* Setting up filters To explore an individual event, click the \[Details] button next to the event for a short overview or open the dropdown menu and click \[View]. Event drop-down menu This will open the event detail view, which includes: * **Event Data** – a summarised view of the data received from your app. Event Data tab * **External Records** – additional fields from the source app, even if they aren't used in the automation. External records tab * **Processes** – the list of automation(s) triggered by this event and the runs it created. You'll also see each run's status (e.g. Completed, Delayed, Cancelled). Processes tab ## Replaying events If an event doesn't trigger an automation as expected, or a run fails before completing its tasks, you can replay individual or multiple events to re-trigger automations and get things back on track. When you replay an event, it can trigger runs across multiple automations at once. Before replaying, always check which automations and runs will be affected, especially if any of them include sending an email or a message. Replaying those without checking first could result in duplicate messages being sent to candidates or contacts. ### What happens when an event is replayed? HireData reprocesses the selected event(s) and triggers the associated automations. The affected tasks will be executed as if the event had just occurred. * **Event-based automations** – For automations that are triggered by a specific event (for example, a candidate reaching a certain stage), the replay will re-trigger the automation immediately based on the event data. If there was previously a created run, it will be replayed and a "Replay" label will show up. An event labeled as Replayed * **Scheduled (one-time) automations** – For automations that run on a fixed date or schedule, replaying the event will not change or reschedule the automation's planned run date. The replay only re-evaluates whether the event matches the automation's conditions. ### How to replay events There are three ways to get to the replay option, depending on what you need: * **From the Events page (all events)** – Navigate to the **Events** page from the main menu. This gives you an overview of all events received by HireData. The Events page * **From a specific automation** – Open the automation you want to investigate, then go to its **Events** page. This filters the view to only show events related to that automation. Finding the Events page for a specific automation The Events page for a specific automation * **From a single event** – Click directly on the event you want to replay to open its detail view. To replay a **single event**, click the three-dot menu next to the event in the detail view or the **Events** list, and select **Replay** from the dropdown. Replaying an individual event To replay **multiple events at once**, check the box next to each event you want to replay on the **Events** page or an automation's **Events** tab. Once one or more events are selected, a **Replay** button will appear at the top of the page. Click it to proceed. Replaying events in bulk To see which automations were previously triggered by the event, open the event and go to the **Runs** tab. This shows you the automations and their status from the last time the event was processed. Use this information to decide whether it's safe to proceed with the replay. Reviewing which automations and runs will be triggered by the replay Check whether any of the listed automations include tasks like **Send Email/Message/Survey**. If they do, make sure you intend for those messages to be sent again before confirming. Once you're confident, confirm the replay. * **Always review the affected automations before confirming a replay.** One event can match multiple automations, and replaying it will trigger all of them. * **Be extra cautious with automations that send emails or messages.** Replaying an event tied to those automations may send duplicate communications to candidates or contacts. * **Use the automation-specific Events tab if you only want to replay within a single automation.** This gives you a more focused view and reduces the risk of unintentionally triggering unrelated automations. * **Bulk replay is useful when multiple events failed at the same time**, for example, after a temporary sync issue. Instead of replaying one by one, you can select all affected events and replay them together. ## Troubleshooting events If an automation didn't run as expected, or you're seeing unexpected data: * Go to the **Processes** tab of the event and check if any runs were created. * Click into the run to view logs and see if a step failed or was skipped. * Compare the **Event Data** with the conditions in your automation to ensure it matches. If no process was triggered, the event likely didn't meet the criteria of any active automations. ### Still need help? If you're unsure why an event didn't trigger your automation or want help interpreting the event data, feel free to contact our team at [support@hiredata.com](mailto:support@hiredata.com). If you do, please include: * A link or the ID of the event; * A link or the name of the automation you expected to be triggered; * Any relevant steps or context that might help us investigate throughout. ## Related topics - [Task History](/pages/task-history.md) - [How to Test an Automation](/automations/how-to-test-an-automation.md) - [Why Didn't My Automation Run?](/knowledge-base/why-didnt-my-automation-run.md) - [Set up a trigger](/apps/custom-apps/set-up-a-trigger.md) - [Runs](/settings/logs/runs.md)