AiHummer
English▾
Sign inAccount
v1.6.x▾
{ }Swagger

Recover an external task without sending it again

v1.6.x · updated 2026-11-15

Some connected tools accept work and return its result later. An operation identifier confirms acceptance, not that your requested outcome has been achieved. For a supported MCP server advertising the Tasks extension, version 1.6 retains that original operation. Ordinary external processing does not require pausing the whole conversation.

Find and read the original operation

  1. Open Connections → External tasks and select the original conversation.
  2. Find the tool’s row. The list includes your operations in that conversation, including work performed by another participating agent.
  3. Choose Read original status. This reads the existing operation without starting the work again.
  4. If the provider limits polling, wait until its next permitted time. A deferred read is not an operation failure.

Recovery requires current access to the conversation, original agent, tool and same external account. Normal renewal of a verified account preserves the operation. If the replacement account cannot be verified, or the service address changes, the receipt remains visible while content and controls close. Creating another operation is not a way around that refusal.

Answer a question

When the original service requires input, read its current state and complete the displayed form. The original user submits the answer. No is a valid answer; an optional field can remain unanswered. Required-field and constraint errors appear beside the form. A number that cannot be transmitted without rounding is not silently changed and sent.

An unsupported question format explicitly reports that no answer was sent. Correct the input and submit a fresh explicit action. If its acknowledgement is lost, first read the original operation: sending the same answer again may duplicate an effect. A genuinely new provider question is distinct from repeating an earlier answer.

Request cancellation and inspect the result

Request cancellation asks the provider to stop the original operation. An acknowledgement does not prove it stopped: completion may have won the race. Read its current status. If the cancellation acknowledgement is lost, do not substitute another cancellation request for readback.

A provider’s completed state does not establish a correct business outcome. A completed response can contain a tool error, shown separately. Read the result and verify the original acceptance conditions. Ordinary text is visible directly; the technical response can be expanded separately.

A send without an acknowledged original identifier is not automatically restarted. Retain its receipt and inspect the original effect using the provider’s available controls. Reviewing uncertain actions and continuing work remain separate steps.

Video-provider operations

A configured video workflow can also retain a provider’s original job identifier. Ask the agent to check that saved operation after interruption rather than order another video. A signed provider notification can update the saved observation, including duplicate notifications, but it does not independently verify the business result. Current-account status polling and result inspection remain separate. Cancellation requests and unknown acknowledgements keep their original history; they must not silently create another paid job. This provider-specific path is distinct from the MCP task list and is available only through the configured supported workflow.