Logs and Transactions answer two complementary questions: what happened during the workflow, and what result was recorded? Knowing which screen to open makes investigation more focused.
Use Logs for context
Logs provide the event trail around an automation. Start here for a failure, skipped action or unexpected state. Read the message, time and identifiers before deciding which setting to change.
Use Transactions for results
Transactions lets you inspect recorded conversion and withdrawal operations. Filter by type or status and use available automation, execution or correlation identifiers to narrow the view. The screen also offers CSV and XLSX export for your own review.
Match the same event
Keep the automation and execution context consistent across both screens. Comparing unrelated records can make a normal result look like a missing step. A conversion record and a withdrawal record represent different operations.
Investigate before editing
An empty filtered list does not prove that an operation never happened. Check the filters first, then compare the event trail with the saved rule.
Build a better support question
Combine the relevant message with non-secret identifiers and the result you expected. That gives support a clear starting point without exposing account credentials.