Skip to content

Propagate cancellation tokens through External Integration Request - #5733

Merged
johnsimons merged 1 commit into
john/cancel_part4from
john/cancel_part5
Aug 11, 2026
Merged

Propagate cancellation tokens through External Integration Request#5733
johnsimons merged 1 commit into
john/cancel_part4from
john/cancel_part5

Conversation

@johnsimons

Copy link
Copy Markdown
Member

This change continues the effort to consistently apply optional CancellationToken parameters to asynchronous methods within the IExternalIntegrationRequestsDataStore interface, its EFCore and RavenDB implementations, and related dispatching services.

Cancellation tokens are now propagated to underlying asynchronous database calls and consuming services. This ensures proper cancellation of long-running operations and further reduces cancellation analyzer debt.

@johnsimons
johnsimons requested a review from rbev August 11, 2026 04:45
@johnsimons johnsimons self-assigned this Aug 11, 2026
@johnsimons
johnsimons marked this pull request as ready for review August 11, 2026 04:46
…ta store

This change continues the effort to consistently apply optional `CancellationToken` parameters to asynchronous methods within the `IExternalIntegrationRequestsDataStore` interface, its EFCore and RavenDB implementations, and related dispatching services.

Cancellation tokens are now propagated to underlying asynchronous database calls and consuming services. This ensures proper cancellation of long-running operations and further reduces cancellation analyzer debt.
@johnsimons
johnsimons merged commit fa72695 into master Aug 11, 2026
98 of 99 checks passed
@johnsimons
johnsimons deleted the john/cancel_part5 branch August 11, 2026 11:55
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