Scheduled or standing work exists in Asana
A monitoring task describes the client, cadence, expected check, and output.
Recurring Jessie work
Scheduled Monitoring
How Jessie Monitoring Asana sections create repeatable reporting and monitoring work without hiding the review trail.
What It Is
Scheduled Monitoring is a workflow, not a separate magic agent. The business process creates recurring or standing Asana work items in Jessie Monitoring sections. Jessie then runs the same context-aware skill flow as normal Asana tasks.
- Use it for recurring reporting, weekly checks, account reviews, and quarterly strategy refreshes.
- Each occurrence should still be inspectable as work in Asana.
- The review trail remains in Asana so consultants can see what ran, what evidence was used, and what Jessie recommended.
Monitoring Flow
Jessie identifies due work
The hosted runtime uses schedule/monitoring state and Asana task context to queue due work.
Context and source assets load
Jessie resolves the Business Unit, approved context, consultant notes, and configured evidence sources.
Skill or generic handler runs
The request routes to a live skill or the generic handler.
AI Gateway interprets evidence
Monitoring output is synthesized through the same LLM-first path where insight is required.
Review output returns to Asana
Jessie comments, attaches artifacts, or asks for clarification.
Asana Sections
| Section type | Meaning |
|---|---|
| Monitoring intake | Candidate recurring checks or standing work that needs enough detail for Jessie to run. |
| Due / active monitoring | Work that is ready to execute on the configured cadence. |
| Review ready | Monitoring output has been produced and needs consultant review. |
| Blocked / needs clarification | Jessie needs more detail, configuration, or source access before it can run safely. |
| Done / archived | The occurrence is complete or no longer active. |
Failure Paths
- Monitoring failures should create visible Asana status rather than disappearing into logs.
- Provider, source, credential, AI Gateway, or context failures should be caveated and tracked as platform issues when appropriate.
- Business clarification needs belong on the task; platform regressions belong in Platform Build Error/Regression.