VOIP-1282-Fix-stale-scheduler-docs - #1158
Merged
Merged
Conversation
Correct stale docs claiming campaign execution and queue timeouts require an external scheduler/cron. Investigation confirmed no such scheduler exists anywhere in the deployment surface, and none is needed: both services self-schedule via delayed RabbitMQ RPC calls to themselves (the same x-delayed-message exchange pattern used throughout the monorepo for internal timers). Neither mechanism is dormant or broken; only the documentation was inaccurate (added by a bulk docs-refresh commit that wasn't derived from tracing the code). - bin-campaign-manager: Fix CLAUDE.md and docs/operations.md to describe the self-perpetuating delayed-RPC execute chain instead of an external scheduler dependency - bin-queue-manager: Fix CLAUDE.md, README.md, docs/domain.md, and docs/operations.md to describe the self-scheduled timeout_wait/ timeout_service delayed RPCs (fired automatically by the queue_join flow action) instead of an external scheduler dependency
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
1 participant
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.
Correct stale docs claiming campaign execution and queue timeouts require an external scheduler/cron. Investigation (VOIP-1282) confirmed no such scheduler exists anywhere in the deployment surface, and none is needed: both services self-schedule via delayed RabbitMQ RPC calls to themselves (the same x-delayed-message exchange pattern used throughout the monorepo for internal timers). Neither mechanism is dormant or broken; only the documentation was inaccurate (added by a bulk docs-refresh commit that wasn't derived from tracing the code).