Repository navigation
feat: run delivery planning from the trigger job - #733
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Base automatically changed from
feat/tra-1277-16-planner-integration-tests
to
main
October 25, 2026 18:43
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
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.
The background worker that picks up the "something happened" ticket and hands it to the planner. If the ticket is nonsense it's thrown away; if the database hiccups it's tried again later. The worker can be plugged into the existing queue runner, but nothing turns the runner on in production yet: that comes with the email/SMS senders.
What changed: the worker, a way to plug extra workers into the queue runner, and an insert-only queue connection, with tests including one full run.
🤖 Generated with Claude Code