Before submitting
Area
apps/web
Steps to reproduce
- Start the app.
- Open any thread in the web or desktop app.
- Attach an image in the composer.
- Observe the orange warning badge on the image.
- Refresh.
- See if the image persisted.
Expected behavior
Attached images should be persisted in composer draft storage when local storage is available. The warning badge should appear only when persistence actually fails.
Actual behavior
The composer verifies persisted attachment IDs before the debounced draft write has flushed to storage. As a result, image attachments can be marked as non-persisted even when storage is healthy, which shows the orange warning badge and makes draft recovery unreliable.
Impact
Major degradation or frequent failure
Version or commit
0.0.13
Environment
No response
Logs or stack traces
Screenshots, recordings, or supporting files
No response
Workaround
No response
Before submitting
Area
apps/web
Steps to reproduce
Expected behavior
Attached images should be persisted in composer draft storage when local storage is available. The warning badge should appear only when persistence actually fails.
Actual behavior
The composer verifies persisted attachment IDs before the debounced draft write has flushed to storage. As a result, image attachments can be marked as non-persisted even when storage is healthy, which shows the orange warning badge and makes draft recovery unreliable.
Impact
Major degradation or frequent failure
Version or commit
0.0.13
Environment
No response
Logs or stack traces
Screenshots, recordings, or supporting files
No response
Workaround
No response