Recover a missing response or changed task

Start by identifying what is uncertain: did the request fail, did the response disappear, or did the project change after you read it? Those situations need different next steps.

A task command has no response

For create_task or update_task, retain the original operation, project address, command key and arguments. Retry that exact command. A matching committed request returns its original acknowledgement; it does not create another task.

After confirmation, read get_task for current content. Another permitted edit may have happened since your original command.

An update reports a conflict

Read the current task and compare it with the work you intended. Submit a new command with the current revision only after deciding how to preserve the newer changes.

A key conflict can also mean that the same key was used with different arguments or another address. Recover the original request instead of guessing which part was saved.

Access is no longer available

Check that the token still has the required permission and that your account can still edit the project. A revoked token, changed membership or unavailable task can prevent both a new write and a replay.

Do not switch to another project’s ID or a broader token simply to force a failed request through. Resolve the intended project’s access first.

The page looks older than the confirmed task

Read the task again or reload the page. A missed live update can be recovered on the next permitted pull. If work remains visibly unsaved, keep that page open and preserve your local changes before attempting recovery.

This preview does not establish that all multi-tab session refresh problems are resolved. A temporary authorization error during refresh is different from a confirmed permission denial.

The external executor stops

Check the executor’s own state before launching another attempt. MCP task access does not establish whether an external process is still running or has already produced an artifact.

Keep the task, original context and returned output together. The managed executor lifecycle, automatic repair and browser-independent continuation of the complete workflow are not qualified in this preview.