Test, enrol and control workflow or sequence runs
Separate dry tests from live enrolment and use run history, pause, resume and cancellation without losing the execution context.
Use these steps in your selected Pixie CRM company workspace. The module, dependent tools and actions available to you follow its configuration and your permissions.
Resource → Test with a record / Enrol a record; Automation → Enrolment history
PermissionManage automation and each action’s capability; native record access; Manage all for permitted control of another initiator’s run
Before you begin
Use a small authorised record for the first test. A dry test explains proposed actions; live enrolment creates a saved run that the worker can execute.
Follow these steps
- Choose Test with a record, select the matching source type and inspect each proposed step. Dry-run delays are explained rather than waited out.
- After independent review and publication, choose Enrol a record and confirm the exact record and resource revision.
- Open Enrolment history, find the run and inspect its current step, due time and recent activity.
- Use Pause for a queued or waiting run. Resume a paused or blocked run only after addressing its cause; the resource must still be published.
- Use Cancel for a queued, waiting, paused or blocked run that should not continue. Process due steps advances a bounded set of your own due work.
Fields and options
- States
- Queued, Waiting, Running, Paused, Blocked, Completed, Goal reached and Cancelled.
- Snapshot
- The run retains the definition and revision enrolled originally. Later edits do not silently replace it.
- Processing
- The manual action handles up to 20 due steps for the initiating identity. The normal CRM cron also advances bounded work; the list shows up to 100 accessible runs.
Rules and limits
- Dry tests do not save profile changes, create live activities, queue email or enrol records.
- Live execution rechecks the original initiator’s current permissions and record access.
- Resuming preserves the due time; cancellation cannot undo actions already completed or recall email already transmitted.
Check the result
- Compare dry-run expectations with the controlled run’s recorded actions.
- Check a cancelled run stops advancing and previously completed actions remain visible.
If something does not look right
- For Blocked, read the reason and repair permissions, record availability or dependencies before resuming.
- For waiting work, inspect due time, execution hours and CRM cron rather than creating a second enrolment.
Common questions
Can another administrator execute the run as themselves?
Control permissions may allow management, but execution remains tied to the original initiator’s identity.
Does Cancel undo a sent email?
No. It stops future run steps; completed external actions are not recalled.