# 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.

Canonical HTML: https://proplix.co.uk/help-centre/marketing-hub-test-enrol-control-runs/

Topic: Sales & Marketing Hub

Reviewed: 13 November 2026

## Where to start

Resource → Test with a record / Enrol a record; Automation → Enrolment history

## 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.

## Fields and options

- **Access needed:** Manage automation and each action’s capability; native record access; Manage all for permitted control of another initiator’s run
- **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.

## Follow these steps

1. Choose Test with a record, select the matching source type and inspect each proposed step. Dry-run delays are explained rather than waited out.
2. After independent review and publication, choose Enrol a record and confirm the exact record and resource revision.
3. Open Enrolment history, find the run and inspect its current step, due time and recent activity.
4. 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.
5. 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.

## 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.

## Troubleshooting

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.

## Fields, 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.

## Questions and answers

### 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.


## Related guidance

- [Sales & Marketing Hub: complete CRM and campaign guide](https://proplix.co.uk/help-centre/marketing-hub-complete-feature-guide/index.md)
- [Build sales follow-up sequences and playbooks](https://proplix.co.uk/help-centre/marketing-hub-sequences-playbooks/index.md)
- [Build a branching CRM workflow with approved dependencies](https://proplix.co.uk/help-centre/marketing-hub-workflow-step-builder/index.md)

Product reference: https://britixo.com/help-centre/marketing-hub-test-enrol-control-runs/
