IAM.Agent: review and recover cloud tasks

Access and availability

These controls belong to the Enterprise and Community development candidates. Obtain the reviewed build and an IAM.Market account with access to an installed agent and sufficient Hosting quota. A marketplace listing, an installation, an agent profile and an execution have different identifiers. Select the installed agent’s profile; do not paste a listing identifier into the execution field.

The operator configures the correct Marketplace environment and account connection. Community also requires IAM_MARKET_ALLOW_RUN=1 to enable submission. This switch grants no account permissions or quota. A local receipt is bound to the configured account and environment; changing credentials can make an earlier receipt unavailable until the original authorized connection is restored.

Community: submit one reviewed task

1. Open ↗ IAM.Hosting, then Load my agents. Choose Installed agent, or enter the supplied Agent profile ID.
2. Enter Exact remote task and Reason for execution. Include only data the selected agent is allowed to receive.
3. Click Prepare review. Compare the displayed agent, complete task, reason, intent identifier and review SHA256 with your intended execution. Preparation does not run the agent.
4. Select I reviewed this exact remote task and approve its account usage and paid compute. Click Approve and send once to submit the reviewed task.
5. Once the receipt contains a run identifier, use Refresh exact run to read its current status and transcript. Acceptance or running is not a completed task. Check the final result and any separately stored artifacts.

Cold startup can take time. Stop waiting, Close, loss of connectivity and closing the application stop local waiting; an accepted cloud execution may continue. Keep the saved intent and run identifier.

Reopen without submitting again

Open IAM.Hosting → Load saved tasks → Open saved task. Compare the selected account, agent and task, then use Refresh exact run. Reading a receipt does not resubmit its task. An unknown outcome stays unknown until the exact remote execution can be reconciled. Do not create an identical replacement solely because the first request timed out.

The native Enterprise client follows the same separate preparation, approval and exact-run recovery contract. Receipts retain their request identity across application restarts. An existing completed or aborted receipt cannot become a new execution through refresh.

Enlarge screenshot

1 2 3

1. Close hosted tasks
2. Load saved tasks
3. Open saved task

This original narrow-screen capture shows the Community candidate reopening an already completed synthetic staging task. It demonstrates layout and receipt recovery; it is not a native mobile application or a new execution.

Request cancellation of one run

1. Open its saved receipt and click Check run controls. Wait for Available for this exact run. Availability is checked against the actual server and the complete account, profile, installation and run identity.
2. Enter Reason to cancel this run. Select I approve cancellation of this exact run. Earlier side effects cannot be undone.
3. Click Request cancellation once. The client durably records this request before dispatch and will not resend it after a disconnect.
4. Use Refresh exact run. A cancellation request or delivery acknowledgement is separate from the host confirming that execution stopped. Only an exact terminal host receipt can establish confirmed stop. Earlier external side effects remain in place.

If the task finishes between discovery and approval, refresh its terminal result; cancellation can legitimately become unavailable. Could not verify server support means no cancellation was sent. A lost cancellation response leaves its outcome uncertain; keep the same saved request and read the exact run rather than sending another cancellation.

If the transcript shows completed after accepted cancellation while remoteStopConfirmed remains false, stopping was not confirmed. Retain the run ID and cancellation time for diagnosis, use Refresh exact run, and do not resubmit the task or cancellation. An error containing cancellation is unconfirmed also does not establish a stopped host; earlier side effects are not rolled back.

Previously installed agents retain their runtime version. If IAM.Market shows Update, wait for the current execution to finish and update that agent before starting a new task. Publishing a new host version does not restart a task already in progress.

Recovery and limits

For 401/403, restore a valid connection and the required account roles. For quota refusal, ask an administrator to review the account’s permitted quota; refreshing a receipt does not allocate more quota. For an unavailable installation, inspect it in IAM.Market before preparing another task.

The Community host serializes short local receipt updates. An interrupted writer can leave an orphan .writelock; subsequent writes fail closed while read-only transcript retrieval remains available. Operator recovery requires stopping all writers for that ledger, checking the exact remote run and removing only the verified orphan .writelock. Never remove the permanent submission or cancellation claim to force another request.

Read service connection instructions and plugin and external-agent instructions before enabling additional tools. The qualified development checks do not establish notarized installers, native Windows qualification or production readiness of every IAM service.