Add task abort feature, compensation context and orchestration/compensation failures monitoring#220
Merged
Add task abort feature, compensation context and orchestration/compensation failures monitoring#220
Conversation
…ess plus completion statuses.
…the revert was triggered.
…oring failed compensations with webhooks.
…webhooks will be notified.
…icking off the orchestration.
…the webhook event in JS Ecommerce example.
… new compensation context for revert handlers.
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
This PR introduces three key improvements:
Task Abort Feature: Allows services to gracefully stop execution with a specific payload rather than raising an error. The abort payload is preserved for compensation handlers.
Enhanced Compensation Context: Compensation handlers now receive context information explaining why compensation was triggered (
failure,aborted, etc.), including the orchestration ID, timestamp, and any relevant payload data.Improved Webhook Monitoring: Added event IDs and detailed payloads to webhooks for better tracking of orchestration completions, failures, and compensation failures. Updated documentation explains how to implement idempotent webhook handling and manage compensation failures.
Documentation updates include:
monitoring-with-webhooks.mdguidecompensations.mdwith context informationResolves #200