Recurring Jessie work

Scheduled Monitoring.

Set up repeatable reporting and monitoring through Jessie Monitoring Asana sections, with the full review trail kept in plain sight.

What It Is

Scheduled Monitoring is a workflow, not some separate magic agent. You set up recurring or standing Asana work items in Jessie Monitoring sections, and Jessie runs them through the same context-aware skill flow as any normal task. Nothing special happens behind the curtain.

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

Scheduled or standing work exists in Asana

A monitoring task describes the client, cadence, expected check, and output.

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.

Evidence quality gates run

Provider-backed outputs must include source evidence and normalized report periods; planning checkpoints are blocked and non-reusable.

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.

Runtime Rules

Standing work is generic Jessie work: KPI checks, reporting steps, client-health checks, data-quality checks, or any other repeatable task body.
Daily metric tasks without explicit dates default to the last 7 complete days ending yesterday, compared with the previous 7 complete days.
Asana project resolution requires active same-environment Business Unit, Asana Source Asset, and project binding records.
Clarification-only artifacts are blocked and non-reusable so they cannot be mistaken for completed work.
Workflow binding schedules are accepted future clock infrastructure for split-out reconciler Workflows; they do not replace Asana task content as the recurring-work instruction source.

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