Repository navigation
Remove HTTP trigger multi-execution-ID feature flag - #814
Merged
Merged
Conversation
The FeatureHTTPTriggerNewExecutionIDsActivePeriod flag has been fully rolled out; always generate execution IDs with the trigger index and drop the legacy fallback path and its cresettings/limiter plumbing. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
bolekk
force-pushed
the
remove_http_flag
branch
2 times, most recently
from
October 7, 2026 16:37
3bacc06 to
cbc1118
Compare
Update expected execution ID calculation to use GenerateExecutionIDWithTriggerIndex (trigger index 0) to match the removal of the legacy EncodeExecutionID fallback path. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
bolekk
force-pushed
the
remove_http_flag
branch
from
October 7, 2026 16:39
cbc1118 to
f8d31ef
Compare
|
bolekk
marked this pull request as ready for review
October 7, 2026 16:48
product-security-plaid-production
Bot
requested review from
amit-momin,
jmank88 and
russell-stern
October 7, 2026 16:48
jmank88
approved these changes
Oct 7, 2026
bolekk
enabled auto-merge
October 7, 2026 17:02
cedric-cordenier
approved these changes
Oct 7, 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
3 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
FeatureHTTPTriggerNewExecutionIDsActivePeriodflag now that it's fully rolled out.generateWorkflowExecutionIDalways usesGenerateExecutionIDWithTriggerIndex; drops the legacy fallback path and thecresettings/limits.RangeLimiterplumbing.multi_trigger_flag_test.go, which only tested the removed flag behavior.Deployment Validation
Confirm HTTP trigger execution IDs continue to be generated with trigger index (no spike in execution-ID errors) in prod dashboards after rollout.
🤖 Generated with Claude Code