Documentation Index
Fetch the complete documentation index at: https://docs.voxworks.ai/llms.txt
Use this file to discover all available pages before exploring further.
Overview
Every time an automation runs, Voxworks records a detailed execution log. The log shows what happened at each step: what data was received, what was sent, how long it took, and whether it succeeded or failed.
There are two ways to view execution logs:
- Global Execution Log — On the main Automations page, the Execution Log tab shows runs across all automations
- Per-Automation Log — On each automation’s editor page, the Execution Log tab shows runs for that specific automation
Reading the Execution Log
Each row in the log represents a single automation execution:
| Column | Description |
|---|
| Status | Completed (green), Failed (red), Processing (yellow), Pending (grey), Dead Letter (red outline) |
| Automation | The automation that ran (in the global log) |
| Time | When the execution started (relative, e.g., “2 min ago”) |
| Duration | Total wall-clock time from start to finish |
| Steps | Completed steps / total steps (e.g., 6/6) |
Per-Step Detail
The expanded view shows each step in order:
| Step | Status | Duration |
|---|
| Transform - Map fields | Completed | 0.01s |
| Upsert Contact - +61400111222 | Completed | 0.15s |
| Upsert Object - monday_item | Completed | 0.12s |
| Create Call - Sales Outreach v2 | Completed | 0.08s |
| — after call completes — | | |
| Transform - Map call results | Completed | 0.02s |
| Sync to Monday.com | Completed | 0.85s |
| Condition - call.rating < 3 | Skipped | - |
- Completed (green) — Step ran successfully
- Failed (red) — Step encountered an error. The error message is shown inline below the step name.
- Skipped (grey) — A condition branch that was not taken
- Processing (yellow) — Step is currently executing
Filtering
The global execution log supports filtering by:
| Filter | Options |
|---|
| Status | Completed, Failed, Processing, Pending, Dead Letter |
| Automation | Select a specific automation |
| Time range | Last hour, Last 24 hours, Last 7 days |
Call Detail Panel
When a call has associated automation actions (either from a Create Call step or a Call Completed trigger), the call’s detail panel shows an Automation Actions section below the Objectives.
This shows the same per-step breakdown as the execution log, scoped to the steps that ran for that specific call. If multiple automations ran for the same call (e.g., one created the call and another triggered on completion), each appears as a separate card.
Error Handling and Retries
When a step fails, the automation engine retries with exponential backoff:
| Attempt | Delay |
|---|
| 1st retry | 10 seconds |
| 2nd retry | 30 seconds |
| 3rd retry | 90 seconds |
| 4th retry | 270 seconds |
| 5th retry | 810 seconds |
- CRM API rate limits — The external API returned 429 Too Many Requests. The retry mechanism usually resolves this automatically.
- Invalid credentials — The connected integration’s access token has expired or been revoked. Re-authenticate the integration in Settings > Integrations.
- Missing required data — A field mapping references a context path that doesn’t exist (e.g., the trigger payload is missing an expected field). Check your field mappings and ensure the source system sends all required fields.
- Timeout — A step took longer than 30 seconds. This usually indicates a slow external API. Consider increasing timeouts or simplifying the request.
Data Retention
Execution logs are retained for 90 days. After 90 days, execution records are automatically deleted. If you need to preserve execution data longer, use a Webhook destination step to forward results to your own data store.
Debugging Tips
- Check the trigger data. Expand the execution and look at the raw trigger payload. Is the data in the format you expected?
- Follow the context flow. Each step shows what it received and what it produced. If a later step fails because of missing data, trace backwards to find where the data was supposed to come from.
- Test with a sample webhook. Use the Test Webhook feature to send a known payload and watch it flow through each step.
- Look at the error message. Failed steps show the exact error. Common ones include HTTP status codes from external APIs, field validation errors, and timeout messages.
- Check the automation is enabled. Disabled automations don’t process triggers. The toggle is on the automations list page.
