feat: Workflow Message Queue (WMQ) support#389
Merged
Conversation
Implements the WMQ feature from conductor-oss/conductor#917: - POST /workflow/{workflowId}/message via WorkflowResourceApi.send_workflow_message - executor.send_message / workflow_client.send_message convenience methods - PullWorkflowMessagesTask for consuming messages inside workflow definitions - TaskType.PULL_WORKFLOW_MESSAGES enum value - WorkflowMessage model (id, workflow_id, payload, received_at) - docs/workflow-message-queue.md usage guide with examples Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
mp-orkes
force-pushed
the
feature/wmq-support
branch
from
c8941a3 to
417a4f6
Compare
v1r3n
approved these changes
Apr 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Implements the Workflow Message Queue (WMQ) feature, allowing external callers to push messages into a running workflow and consume them inside the workflow via a system task.
executor.send_message(workflow_id, payload)/workflow_client.send_message(...)→POST /workflow/{workflowId}/messagePullWorkflowMessagesTaskfor consuming messages inside workflow definitionsTaskType.PULL_WORKFLOW_MESSAGESenum valueWorkflowMessagemodel (id,workflow_id,payload,received_at)docs/workflow-message-queue.mdServer requirement
conductor.workflow-message-queue.enabled=truemust be set on the Conductor server.Test plan
PullWorkflowMessagesTaskexecutor.send_message(workflow_id, {...})and verify a UUID is returnedmessages,count)404when workflow ID is unknown409when workflow is not inRUNNINGstate429when queue is at capacityRelated
🤖 Generated with Claude Code