Logs provide the event trail behind an automation. They are the place to start when a rule appears paused, an action was skipped or a result differs from what you expected.
Investigate an event
- Open Logs from the navigation.
- Use the available filters to narrow the activity you are investigating.
- Read the event message and record its relevant time and identifiers.
- Compare it with the automation's saved configuration and state.
- Open Transactions when you need to review the recorded financial operation.
Separate an event from an outcome
A log explains activity; a transaction records a conversion or withdrawal result. Reading both helps avoid interpreting a setup or skipped-action message as a completed transaction.
Make one informed change
Use the visible event to identify which setting or connection check needs attention. Repeatedly editing a rule without understanding the event makes the next result harder to interpret.
Prepare useful support context
Include the automation identifier, visible error text and approximate time. Omit passwords, keys, authentication codes and unrelated account details.