Know Exactly What Your Automation Did
Execution logs show every action, data capture, and warning so you can debug and optimize with confidence.
Debug Without Guesswork
Clear logs make it easy to see which step failed and why. When an automation behaves unexpectedly, the first question is almost always: what did the workflow actually do? RTILA X execution logs answer that question with a step-by-step record of the run.
Instead of guessing whether a selector was wrong, whether a page loaded correctly, or whether a network request failed, you can inspect the log and see exactly what happened. This reduces debugging time and makes it easier to hand off projects to teammates.
What Gets Logged
Execution logs capture the important details of every run:
- Navigation URLs and page titles
- Command name and configuration summary
- Selector and element matching results
- Extracted value counts and previews
- Wait and timeout events
- Warnings and error messages
The level of detail is balanced: enough to debug a problem, but not so much that the log becomes unreadable. You can expand individual entries to see full data when needed.
Live Memory Monitor
The memory monitor shows how much system memory the current workflow is consuming. This is especially useful during long or heavy extraction tasks. If memory use climbs unexpectedly, you can pause the run, adjust settings, or split the job before the system becomes unstable.
Memory monitoring is also a good early warning signal. A slow increase over many pages may indicate that captured data is not being cleared properly, while a sudden spike may point to a particularly large page or an embedded resource that consumed excessive memory.
Session History
Every run is stored in session history, so past executions remain available after the workflow finishes. You can open a previous session to review what happened, compare results between runs, or check whether a site changed its behavior over time.
Session history is especially valuable for recurring schedules. You can look back at the last month of daily runs, see when an error started appearing, and pinpoint the exact date a target site changed.
Exporting Logs
You can export execution logs for external analysis, documentation, or support tickets. The exported log is a plain-text or structured file that includes timestamps, command details, and error messages. This makes it easy to share the context of an issue without sharing your entire project.
Exporting logs is also useful for audits. If you need to demonstrate that a workflow ran correctly, collected the expected data, or handled errors gracefully, the log provides a clear record.
Debugging with Logs
The standard debugging flow looks like this:
- Open the session for the run that failed.
- Find the command where the error occurred.
- Review the selector, page state, and error details at that step.
- Adjust the command or add a wait condition.
- Resume from the checkpoint and verify the fix.
This loop is fast because you do not need to re-run the entire workflow to test a correction. Checkpoint and resume lets you begin near the failure point, and the log tells you exactly what to fix.
Monitor Over Time
Track trends across runs so you can spot reliability improvements or regressions. Logs reveal not just individual failures, but patterns that help you build more resilient automations.