Repository navigation
Let chat orchestration run existing durable workflows #1551
Description
Summary
Part of #1543 (Phase 5). Add a workflow_run capability so a chat orchestration plan can start one of the user's existing durable workflows and link to the run.
User Value
"Run my weekly digest now" should work from chat. The user doesn't have to find the workflow, open it and press Run.
Proposed Behavior
workflow_run(Gather) works only for durable workflows from the Phase 4 catalog. Non-durable manual runs execute synchronously with the session's roles (route_backend_workflows.py:2753-2800), so they get an unavailable reason instead.request_id = uuid5(orchestration_run_id, step_id), so a retried step never starts a second run.- The run records
trigger_source: 'chat_orchestration'andinvocation_metadata. effects_uncertainapplies.- A new capability descriptor,
approval_floor: 'manual', enforced infunctions_orchestration_schema.py:972-1042, so a plan that runs a saved workflow always needs manual plan approval, whatever the admin's approval mode. Nothing like it exists today. - The step starts the run and links to it. Posting the results back into the chat is Phase 6b.
Acceptance Criteria
- "Run my weekly digest now" asks for manual plan approval even when approval is Auto, queues exactly one run, and links to it.
- Retrying the step or the plan doesn't start a second run.
- Non-durable workflows show a clear unavailable reason.
- Functional tests for the approval floor, idempotent request IDs, and registry and admin option equality.
- Feature doc, release notes and
config.pyversion.
Notes
- Roadmap: §6, Phase 5. Related gotchas in §8: 6 (Auto plan approval), 12 (authorization drift over months), 18 (admin capability options test).
- Depends on: Phase 4 (Let chat orchestration propose workflows with an Approve, Deny and Edit card #1547). Phase 6b (Post workflow results back into chat and answer follow-ups from them #1546) depends on this.
Metadata
Metadata
Assignees
Type
Projects
- Status
Activity
Link workflow runs through the reviewed workflowRunHref builder
Clear CodeQL notes in workflow run code
Start a saved workflow from a chat plan: the workflow_run adapter
Move Phase 5 to version 0.261.212
Link the workflow runs a chat plan started (Phase 5, #1551)
Keep workflow run log codes in Application Insights
Document starting saved workflows from chat (Phase 5, #1551)
paullizer commentedon Oct 1, 2026
Phase 5 merged
#1594 merged into
paullizer-react-v2-uias 5fc50a5 (0.261.212). It's behind the new admin setting Run Workflows From Chat (enable_chat_orchestration_workflow_runs), which is off by default.Acceptance criteria
CHAT_ORCHESTRATION_WORKFLOW_RUNS.md, release notes and the version.Validation on #1594's final head (678f56c)
-O. The link-route suite: 63/63.functions_appinsights.py(code scanning alerts 2552, 2553 and 2554). Phase 5: orchestration runs existing workflows (workflow_run, start-and-link) #1594 doesn't change that file.Not in this phase
Posting the result back into the chat is Phase 6b (#1546). For now, the chat answer says where the results will appear and links to the run.
Follow-ups
log_event's existing sanitizing visible to CodeQL, so those log-injection annotations stop appearing on PRs. A separate PR will handle this.This issue is ready to close.