Playbook workflow resolution always reads the system org #1091

Closed
opened 2026-10-27 13:38:59 +00:00 by sam · 0 comments
Owner

LivePlaybooks.Dispatch resolves with a background context, so a task in any org is matched against the system org's eda-playbooks document instead of its own. Done when dispatch resolves against the task's org.

Acceptance criteria

Playbook dispatch resolves the workflow document from the dispatched task organization.

Close reason

Dispatch now takes the task's context (principal and org from workflowContext) and LivePlaybooks keeps one compiled set per org


Imported from beads archie-core-5t4z7 · GitHub #1583 · type bug · priority P2 · created 2026-10-10 · closed 2026-10-13

LivePlaybooks.Dispatch resolves with a background context, so a task in any org is matched against the system org's eda-playbooks document instead of its own. Done when dispatch resolves against the task's org. ### Acceptance criteria Playbook dispatch resolves the workflow document from the dispatched task organization. ### Close reason Dispatch now takes the task's context (principal and org from workflowContext) and LivePlaybooks keeps one compiled set per org --- _Imported from beads `archie-core-5t4z7` · GitHub #1583 · type bug · priority P2 · created 2026-10-10 · closed 2026-10-13_
sam added the mediumbug labels 2026-10-27 13:38:59 +00:00
sam self-assigned this 2026-10-27 13:38:59 +00:00
sam closed this issue 2026-10-27 13:38:59 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#1091