Self Checks
Dify version
Cloud version
Cloud or Self Hosted
Cloud
Steps to reproduce
- Run a published Dify Cloud workflow containing Python Code nodes through POST
https://api.dify.ai/v1/workflows/run.
- During normal shadow traffic on September 14, 2026, between 12:43 and 14:01 UTC, executions
repeatedly failed with:
Got error code: -500.
Got error msg: open /var/sandbox/sandbox-python/tmp/.py:
no space left on device
- Our export contains 6,543 failures with this error. During 13:00–14:00 UTC, all 4,953 workflow
runs failed.
- Successful processing resumed after approximately 14:01 UTC.
We cannot reproduce the storage exhaustion on demand because the sandbox infrastructure is managed by
Dify Cloud. We can provide affected run IDs and sanitized logs for investigation.
✔️ Expected Behavior
Python Code nodes should execute reliably without failures caused by exhausted temporary storage.
Dify Cloud should maintain sufficient sandbox capacity and automatically clean up temporary execution
files. Infrastructure failures should not cause a prolonged outage across otherwise valid workflow
requests.
❌ Actual Behavior
No response
Self Checks
Dify version
Cloud version
Cloud or Self Hosted
Cloud
Steps to reproduce
https://api.dify.ai/v1/workflows/run.
repeatedly failed with:
Got error code: -500.
Got error msg: open /var/sandbox/sandbox-python/tmp/.py:
no space left on device
runs failed.
We cannot reproduce the storage exhaustion on demand because the sandbox infrastructure is managed by
Dify Cloud. We can provide affected run IDs and sanitized logs for investigation.
✔️ Expected Behavior
Python Code nodes should execute reliably without failures caused by exhausted temporary storage.
Dify Cloud should maintain sufficient sandbox capacity and automatically clean up temporary execution
files. Infrastructure failures should not cause a prolonged outage across otherwise valid workflow
requests.
❌ Actual Behavior
No response