The Run Debug feature in ReadiNow's Process Builder is used for testing and troubleshooting a process without assigning steps to actual end users. It simulates the process flow with admin privileges, helping builders validate the logic, data flows, and configurations.
What Run Debug Helps With
- Step-by-Step Execution
- You can walk through each stage, block, and step as though you're the assigned user.
- Bypass Assignment Restrictions
- It ignores security role assignments, allowing you to see all steps regardless of permissions.
- Test Without Notifications
- No tasks or alerts are sent to real users, avoiding interference with live operations.
- Validate Expressions and Inputs
- See how expressions resolve, which records are affected, and whether step inputs are working as expected.
- Check Visual Flow
- See chevrons, transitions, and action button behaviour live as it would appear to users.
- Debug Complex Paths
- Ideal for testing conditional logic, skipped steps, loops, and error handling.
How to Use It
- Go to the Process Builder or Process List.
- Click Run Debug on a saved version of the process.
- Interact with the process in the same UI used by end users, but with full control and visibility.
Sample Debug Run for the Employee Onboarding process
- User starts the Debug Run for this process.
- User fills in the necessary form fields and progresses through the form until the first process related button is clicked. In this case Submit Request.
On the debug screen you will find helpful information such as:
- Run mode: with below possible values
- Debug for process that are run through Debug Run
- Launch for processes that are run normally through the solution
- Run status: with below possible values
- Running
- Complete
- Error
- Stage name: only the stages that have run will appear
- Flow Type: the flow type pf the block hat is hosting the running step
- Step status: shows the status of steps that have run or are running
- Start and End date/time of the steps
- Step type: such as Display Page
- Step Assigned To: the person who can execute the buttons
- The button that was clicked in the step, such as “Approve”
- The Input and Output details of the step

When you start filling in the form you will see that the Run Debug floating form is updated.
After the user clicks on the first process button the Step will be executed and the flow moves to the next step.
The step process that was “Running” before is now “Complete” and the End time is filled.
Submit Request appearing in yellow below was the button that was clicked by the user.
When you scroll the form down you will see info for the next step which is still Running.
In the below screenshot we see results form when the user clicked on the Approve button of the DH Approve/Reject step that is in the Approval stage.
The final stage now, Onboarding, has the HR Start Process step running.
After the user clicks on the final button Complete in the Complete Onboarding step the process ends displaying a message similar to the below
Below is a screenshot of the complete process with “Show more” expanded.
Key Reminder:
- Debug mode doesn’t respect live record-level or task access controls.
- Use it only for testing—not for real data submissions or production use.