Skip to content

fix: enforce TaskListActivitiesPerSecond in matching#7575

Merged
timl3136 merged 1 commit intocadence-workflow:masterfrom
timl3136:fix/TaskListActivitiesPerSecond
Jan 7, 2026
Merged

fix: enforce TaskListActivitiesPerSecond in matching#7575
timl3136 merged 1 commit intocadence-workflow:masterfrom
timl3136:fix/TaskListActivitiesPerSecond

Conversation

@timl3136
Copy link
Member

What changed?
Added rate limiting to directly dispatched activities. Modified OfferOrTimeout() in service/matching/tasklist/matcher.go to check rate limits before dispatching tasks, matching the behavior of the normal Offer() method.

Why?
Activities dispatched via history.maxActivityCountDispatchByDomain were skipping the TaskList rate limiter entirely. This meant the TaskListActivitiesPerSecond config only worked for normal activities but not for directly dispatched ones.

How did you test it?
unit tests

Potential risks

Release notes

Documentation Changes

Signed-off-by: Tim Li <ltim@uber.com>
@timl3136 timl3136 changed the title Add a fix to enforce TaskListActivitiesPerSecond in matching fix: enforce TaskListActivitiesPerSecond in matching Dec 31, 2025
@timl3136 timl3136 merged commit 68d1592 into cadence-workflow:master Jan 7, 2026
42 of 44 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants