JDBC bulkdataload serverless dataflows stuck in deleting state
· 2 min read
Serverless Dataflows Occasionally Stuck in Deleting State
Affected Versions: 2.7 3.0 3.0.3 3.0.6
Fix Version: 3.1
Root cause(s)
In rare cases, serverless dataflows can get stuck in deleting state due to timing issues. The specific problems identified:
- Serverless dataflows go through multiple setup phases before becoming running
- Users cannot perform stop or delete operations during these setup phases
- Previous implementation did not handle these phases properly
- Users received misleading success confirmations when operations actually failed
The fix involved adding proper validation to ensure users receive accurate feedback when attempting operations during invalid phases.
Impact
- Serverless dataflows sometimes appeared stuck in "deleting" state with no clear resolution path through the UI
- Users could not effectively manage affected serverless dataflows
Mitigation
Workaround
- Automatic resolution: The task will either be deleted automatically after approximately 30 minutes
- Use API instead of UI: If the delete button is unavailable or automatic deletion doesn't occur after 30 minutes, use the API to delete the dataflow
Fix available
Fix is available in Amorphic version 3.1. Users now receive accurate error messages when attempting operations during invalid phases.
Timeline
- 2025-09-16: Bug reported/identified (CLOUD-6280)
- 2025-09-16: Debug and root cause analysis completed
- 2025-09-17: Workaround provided and fix completed
- 2025-09-22: Patch available in Version 3.1
