Troubleshooting Workflows

Troubleshooting Workflows

When a workflow does not behave as expected, WRRK provides tools to diagnose and fix the issue.

Workflow Logs

Every workflow execution is logged. To view logs:

1. Go to Workflows and click on the workflow in question.
2. Click the Logs tab.
3. Each log entry shows:

• Timestamp — When the workflow ran.
• Trigger Event — What triggered the execution.
• Steps Executed — Each action and whether it succeeded or failed.
• Error Details — If a step failed, the specific error message.

Common Issues

Workflow not triggering:

• Verify the workflow is Active (not paused or draft).
• Check the trigger conditions — they may be filtering out the events you expect.
• Ensure the connected channel or module is working (e.g., email sync is active).

Actions not executing:

• Check the workflow logs for error messages.
• Verify that action parameters are correct (e.g., valid email address, correct WhatsApp template name).
• For webhook actions, ensure the target URL is reachable and returns a 2xx status code.

Emails not sending:

• Verify your email account is connected and syncing.
• Check for rate limiting — sending too many emails too quickly may trigger provider limits.
• Review the email content for issues that might trigger spam filters.

Duplicate executions:

• Check if you have multiple workflows with the same trigger.
• Add conditions to prevent a workflow from firing more than once per contact/deal.

Testing Mode

Use the Test button on any workflow to simulate execution:

1. Click Test in the workflow builder.
2. Select or create sample data.
3. The system walks through each step, showing what would happen.
4. No actual messages are sent or records modified during testing.

Pausing Workflows

If a workflow is misbehaving, you can pause it immediately:

1. Go to Workflows.
2. Click the toggle next to the workflow name to switch it from Active to Paused.
3. Investigate and fix the issue using logs and testing.
4. Re-activate when ready.

Getting Help

If you cannot resolve the issue, contact support with:

• The workflow name and ID.
• The relevant log entries.
• A description of expected vs. actual behavior.