feat(engine): propagate InitiatedByUserId through ranking and online strategies#239
Merged
Merged
Conversation
aaron-iz
approved these changes
May 12, 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
Threads
InitiatedByUserIdfrom incoming scheduling requests into everySchedulingResultthe Engine emits, so RabbitMQ result messages can be attributed to the operator who triggered the run.Changes
RankingAlgorithmStrategy: Success, error, empty-activity, missing-period, and catch paths includeperiodRequest.InitiatedByUserId.OnlineMatchingStrategy: All returns include initiator from the constraint request;TryRescheduleAssignmentAsyncextended withinitiatedByUserIdand wired from both activity and user constraint flows.Testing
dotnet buildChronos.Enginedotnet testChronos.Tests.Engine (or full test run)Risk / rollout
Low–medium. Touches many code paths in online matching; behavior for algorithms is unchanged aside from an extra field on the result DTO. Coordinate deployment: Engine should be deployed after or with MainApi publish that sets initiator on requests, otherwise results may still have
nullinitiator until both sides align.Files in this PR (only)
Chronos.Service/src/Chronos.Engine/Matching/RankingAlgorithmStrategy.csChronos.Service/src/Chronos.Engine/Matching/OnlineMatchingStrategy.cs