Who This Is For / When to Use
This article is for Kyrios users building or modifying workflows who need to validate actions, timing, and logic before allowing real contacts to enter automation.
Use this before publishing a workflow or after making changes to an existing workflow.
Why Testing Workflows Is Important
Testing workflows ensures automation behaves as expected before affecting real contacts.
Testing helps you:
Confirm each action executes correctly
Identify configuration errors early
Validate wait steps, conditions, and branching logic
Prevent broken emails, SMS messages, or misrouted contacts
Testing workflows before publishing reduces automation errors and support issues.
Testing Methods Available in Kyrios
Kyrios provides multiple ways to test workflows depending on what you need to validate.
Available Testing Tools
Test Workflow button: Runs the workflow manually using a selected contact
Execution Logs: Shows step-by-step execution results and errors
Manual step advancement: Allows moving contacts forward during testing
Organic testing: Triggers the workflow naturally using real trigger conditions
Important Setting: Allow Re-Entry
The Allow re-entry setting controls whether a contact can enter the same workflow multiple times.
When testing repeatedly with the same contact:
Use a new test contact, or
Temporarily enable Allow re-entry in Workflow Settings
If re-entry is disabled, previously enrolled contacts may be skipped during testing.
Part 1: Running a Test Workflow
Step 1: Access the Test Workflow Feature
The Test Workflow button allows you to run a workflow without triggering it organically.
Steps
Open Automation → Workflows.
Select the workflow to test.
Click Test Workflow in the top-right corner of the builder.
Important: Test Workflow skips the initial trigger and starts from the first action.
Step 2: Select a Test Contact
A test contact is required to simulate workflow execution.
Steps
Choose a contact from the dropdown.
Click Run Test.
Some actions may behave differently than organic triggers due to skipped trigger data.
Part 2: Reviewing Execution Logs
Execution Logs show exactly what happened during each workflow action.
Step 3: Open Execution Logs
After running a test, review the workflow’s execution history.
Steps
Open the workflow.
Click the Execution Logs tab.
Filter by contact, date, status, or action if needed.
Step 4: View Execution Details
Each workflow run provides detailed execution data.
Steps
Locate the workflow execution entry.
Click View Details or View Execution History.
Execution details reveal errors such as missing custom values, invalid conditions, or blocked actions.
Part 3: Manually Advancing Contacts During Testing
Manual step advancement helps test waits, replies, and time-based conditions.
When to Use Manual Advancement
Testing long wait steps
Skipping delays during QA
Forcing contacts to the next action
Manual advancement does not change workflow logic and is only used for testing.
Part 4: Testing SMS and Email Actions
Testing SMS Actions
SMS actions include a built-in test feature.
Steps
Open the SMS action.
Enter a phone number (include country code).
Click Send Test SMS.
Limitations:
Links may not work correctly
Custom values may not populate
Messages may be blocked by spam filters
Testing Email Actions
Email actions also support test sends.
Steps
Open the Email action.
Enter one or more test email addresses.
Click Send Test Mail.
Limitations:
Custom values may not populate
Links may break
Use a different inbox to avoid spam filtering
Part 5: Post-Testing Cleanup
Test data should be removed before publishing workflows.
Step 5: Remove Test Contacts
After testing:
Remove test contacts from the workflow
Confirm no test contacts remain enrolled
This prevents outdated test data from interfering with live automation.
Best Practices for Workflow Testing
Use fresh test contacts when possible
Test organically using real triggers when accuracy matters
Review execution logs after every change
Pause workflows before editing live automations
Validate SMS and email content outside test mode
Common Issues and Fixes
The Workflow Did Not Run During Testing
Cause: Contact already enrolled or re-entry disabled.
Fix: Use a new contact or enable Allow re-entry.
Actions Failed During Testing
Cause: Missing custom values or incomplete configuration.
Fix: Review Execution Logs and update action settings.
Messages Look Incorrect in Test Sends
Cause: Test mode does not fully populate dynamic values.
Fix: Run an organic test using real triggers.