Dataflow auto-retry mechanism is not working as expected
· 2 min read
Dataflow auto-retry mechanism is not working as expected
Affected Versions: 3.0
3.0.3
3.0.6
Fix Version: 3.1
Root cause(s)
A bug was introduced in version 3.0 that affects how retry intervals are processed during dataflow operations. The specific problems include:
- The system incorrectly processes retry interval values multiple times during dataflow operations
- Each processing operation converts the retry value again, causing it to grow exponentially
- User-configured retry intervals are not preserved as originally set
- Dataflow recovery takes much longer than intended due to incorrect retry intervals
Impact
- User configured retry intervals become much larger than intended after dataflow operations
- Dataflows take much longer to recover from failures than you expect
- Retry configurations become effectively unusable due to the exponential growth
- Unpredictable dataflow recovery behavior that doesn't match your settings
Mitigation
Fix available
Fix is available in Amorphic version 3.1. The system now correctly preserves your configured retry intervals throughout all dataflow operations, ensuring they remain as you originally set them.
Timeline
- 2025-08-17: Bug reported/identified (CLOUD-5908)
- 2025-08-17: Bug triaged and documented
- 2025-08-18: Root cause analysis, fix development and testing completed
- 2025-08-18: Solution merged and released in Version 3.0.8