generated from amazon-archives/__template_Apache-2.0
-
Notifications
You must be signed in to change notification settings - Fork 4
Open
Description
Context
Implement handling of recoverable errors in serialization/deserialization operations to improve reliability and user experience.
This is actually already done, but should align with Task 15, when revisiting final error naming.
Technical Requirements
- Serdes errors terminate execution immediately by raising unhandled exception. The backend will retry these.
- Serdes actually already does this by throwing a FatalError.
Implementation Details
- File:
src/aws_durable_execution_sdk_python/serdes.py - Error Types: Network errors, temporary service issues, format errors
- Recovery Strategy: Retry with backoff for recoverable errors
Acceptance Criteria
- Recoverable errors are properly identified
- Retry logic implemented for recoverable errors
- Non-recoverable errors fail fast with clear messages
- Data integrity maintained during recovery
- Error classification is well-documented
Priority: Low
Estimated Effort: 0.5 days
Metadata
Metadata
Assignees
Labels
No labels