Sequence Status and Lifecycle
Understand draft, active, paused, and archived sequence states
Each sequence has a lifecycle status that controls whether it can execute.
Draft
Default state for newly created sequences.
- Editable
- Not executed automatically
- Good for building and testing configuration
Active
Production state.
- Eligible for execution and automation
- Required for event-based trigger firing
- Required for execute API enrollment
Paused
Temporary stop state.
- New enrollments should stop
- Use when adjusting logic or content
- Resume by switching back to Active
Archived
Long-term inactive state for old workflows.
- Kept for history/audit context
- Not used for current automation
Activation Rules
You cannot reliably operate a sequence in production without:
- Active status
- At least one valid step
- Correct trigger path (event or API)
Recommended Lifecycle Pattern
- Build in Draft
- Activate for pilot cohort
- Pause to tune if needed
- Reactivate for scale
- Archive obsolete versions
Governance Tips
- keep clear naming/versioning (
v1,v2) before archiving old flows - pause before high-impact edits to active production sequences
- verify trigger path after reactivation, especially for event-based automations
For failure diagnosis, see Sequence Troubleshooting.
// Related articles
Creating Your First Sequence
Build and activate an automated multi-step sequence for survey and follow-up workflows
Sequence Settings Reference
Understand all sequence-level settings and how they affect delivery behavior
Event-Based Automation
Automatically run sequences when specific response events occur
Sequence Troubleshooting
Diagnose why sequences are not running or certain steps are skipped
Was this article helpful?
Let us know if you found this article helpful or if you need more information.
Join hundreds of businesses already using demeterrr to collect feedback, boost reviews, and grow faster.
Start Your Trial