Should I send again after a connection error?

First check Task board. The desktop may have accepted the task before its response was lost, so immediately sending again can create duplicate work.

Before you begin

Task status describes execution, not whether the result is factually correct or ready to publish. Keep the original input and inspect the actual output file. Task details, results and execution events provide different evidence; use them together when deciding whether to accept, revise or retry work.

Steps

1. Keep the current composer and attachments open.
2. Use Reconnect when the office stops refreshing.
3. Look for the submitted task in Task board.
4. Resend only after confirming its absence.

Example

If the brief remains in the composer after an error but a matching task is already queued, open that task instead of submitting a second copy.

Check the result

Compare the brief, teammate and creation time to identify the accepted task.

Limits and troubleshooting

Unsent drafts are preserved in the current view, but not promised across closing or reloading the app. Copy important text before restarting.