Console workflow runs
Save the graph in the workflow designer, review its connections, and launch it with the intended trigger data. A successful launch response means Temporal accepted the request; it does not mean the work finished. Open Run history and refresh the record to inspect:pending: the request is saved, but worker start has not yet been recorded.running: the worker recorded its start.completed: the selected steps completed and the final result was saved.failed: a step or workflow operation failed. Inspect recorded steps before retrying side effects.cancelled: cancellation was observed and the worker saved the final outcome.
proof_status: "not_generated" explicitly means no bundle was generated. A zero recorded cost does not establish that an external provider charged nothing.
Email notification step
Use one recipient per step and supply explicit text:provider_accepted and a message identifier after the configured SMTP provider accepts the message. It does not guarantee inbox delivery. Named templates, multiple recipients in one step, and non-email channels are not supported by this activity. Automatic retries are disabled because SMTP cannot guarantee exactly-once delivery. Investigate an unconfirmed attempt before sending again.
Execution boundaries to account for
- A launch timeout can leave a
pendingrecord even if Temporal accepted the request. Check that run before launching another; automated dispatch reconciliation remains incomplete. - Console human-review steps persist assigned approval requests. Authorized approve/reject decisions and their Temporal outcomes have passed scoped live acceptance. A separate MAIP agent-approval record does not signal a Console workflow.
- AI steps use the configured Gemini gateway; a synthetic Temporal-to-Gemini run has passed live acceptance. Validate your own prompt, output requirements and costs.
- External
tool_callsteps are not available in the deployed connector runtime. Keep these graphs as drafts; they cannot be used for production tool automation. An external integration package does not enable a workflow connector. - A background worker reconciles known Temporal execution identifiers, including terminal failure and continued-as-new transitions. It does not infer successful effects from missing history, and cannot recover an unknown dispatch identity.
- Workflow definitions, runs, steps and approvals created after environment isolation are scoped to the selected workspace environment. Historical records without verified environment attribution remain available to platform oversight; they are not silently assigned to production. Broader provider-side isolation and all external side-effect recovery are not established by this storage boundary.
- Workflow audit events are saved with state changes. This does not establish completed export to every external audit destination or an independently certified retention policy.
MAIP execution tracking
The public orchestration execution reference documentspattern, orchestrator_id, and agent_ids. Use its generated fields and dropdowns for the complete request contract.
An HTTP 201 response creates a tracking record. Its initial running status is not proof that agents or tools ran. Execute and supervise those actions in your application until a supported executor is connected.
The MAIP workflow run reference is a separate record-creation route requiring trigger_agent_id. Do not substitute Console graph IDs or assume that a supplied schedule registers a Temporal schedule.
New automatically generated MAIP receipts use the configured managed signer. Verify a receipt through the receipt verification API. Its signature authenticates the recorded statement; it does not prove that an unexecuted business action occurred. Some preserved historical records have unverifiable placeholder signatures.
For independent human decisions about a proposed agent action, use agent approvals. Approval records do not automatically execute or resume a workflow.
