Definition #
Agent Lifecycle and Release describes how an Agent moves from initial draft to validated production use.
It covers editing, reviewing, testing, approving, and releasing changes in a controlled process.
Why it matters #
A defined release lifecycle reduces regressions, protects live candidate experience, and improves team accountability.
How it works #
- Build or update Agent in draft.
- Review key changes (routing, widgets, integrations).
- Test critical candidate paths.
- Approve change using role-based control.
- Release to production.
- Monitor behavior and logs after release.
Configuration fields #
- Draft vs live state indicators
- Release owner and approver
- Change scope (paths/steps/widgets)
- Validation checklist status
- Rollback plan reference
- Post-release monitoring window
Example scenario #
A team updates journey completion messaging and compatibility criteria.
They test in non-production, get approval, release during low-risk hours, and monitor candidate progress metrics for the next day.
Common mistakes #
- Releasing multiple major changes at once
- Missing rollback strategy before publish
- Skipping smoke tests after release
- No owner assigned for release monitoring
Troubleshooting checklist #
- Confirm what changed in this release
- Compare pre-release and post-release behavior
- Isolate whether issue is configuration or integration related
- Re-run high-impact path tests
- Decide fix-forward vs rollback quickly
- Record root cause and prevention note