Test and Debug Workflows

A workflow that looks right in the builder can still fail at runtime. Testing before activation and monitoring execution logs afterward keeps your automations reliable.

Test Mode

Every workflow has a Test button in the builder. Here is how to use it:

1. Open your workflow and click Test Workflow in the top-right corner.
2. JustCall generates sample data that matches your trigger type (for example, a sample missed call event for a call.missed trigger).
3. The test runs through your conditions and actions using this sample data.
4. Results appear in a panel showing which conditions passed, which actions executed, and what output each action produced.

Test mode does not send real SMS messages, create real CRM records, or post to Slack. It simulates the entire sequence so you can verify logic without side effects.

Live Testing

Once you are confident the logic is sound, do a live test:

1. Activate the workflow.
2. Trigger the event yourself — for example, call your JustCall number and let it go to voicemail.
3. Check that each action executed as expected (SMS received, CRM record created, Slack message posted).
4. Open the execution log to confirm all steps completed.

Execution Logs

Every workflow run is recorded in the execution log. Access it from Settings → Workflows → [Your Workflow] → Logs.

Each log entry includes:

• Timestamp — When the workflow ran.
• Trigger data — The event payload that started the workflow.
• Condition results — Which conditions passed or failed.
• Action results — Success or failure status for each action, with response details.
• Duration — Total execution time.

Use filters to view only failed runs, runs from a specific date range, or runs involving a particular agent or number.

Common Issues and Fixes

CRM Authentication Expired

Symptom: CRM actions fail with a 401 or "unauthorized" error. Fix: Go to Settings → Integrations, disconnect and reconnect your CRM. Then re-test the workflow.

Field Mapping Errors

Symptom: CRM records are created but fields are blank or contain wrong data. Fix: Open the workflow action and verify that each JustCall merge field maps to the correct CRM field. Pay attention to field types — a CRM "number" field will reject text input.

Rate Limits

Symptom: Actions fail intermittently with 429 or "too many requests" errors. Fix: Reduce the number of workflows sharing the same action type, or add conditions to limit how often the workflow triggers. For webhook actions, check the destination server's rate limits.

SMS Not Delivered

Symptom: The action shows as "success" but the recipient did not receive the text. Fix: Check the SMS delivery log under Messages. Common causes include invalid numbers, carrier filtering, or opt-out status.

Webhook Timeout

Symptom: Webhook action fails with a timeout error. Fix: JustCall waits up to 10 seconds for a webhook response. If your endpoint takes longer, optimize its response time or return a 200 status immediately and process asynchronously.

Debugging Checklist

1. Check the execution log for the specific run that failed.
2. Identify which step failed — condition evaluation or a specific action.
3. Review the error message and response code.
4. Fix the root cause (re-auth, re-map, adjust conditions).
5. Re-test using Test Mode, then trigger a live test.

Best Practices

• Review execution logs weekly, even for workflows that appear healthy.
• Set up a Slack notification workflow that alerts you when another workflow fails — automation watching automation.
• Keep a changelog of workflow edits so you can roll back if a change causes failures.

Testing is not a one-time step. Treat it as an ongoing practice to keep your automations running smoothly.