Run an existing scheduled bot once
run_deployment_onceHIGH RISK: request owner approval for one immediate iteration of an existing scheduled bot. Use this for run once, an extra run, or retrying a missed iteration. It can place live trades. Preserves the saved revision, broker, variables, recurring schedule, history and state. Current balance and holdings reports are not prerequisites; use the exact saved deployment and broker connection status. Preparation reads the saved connection status and mode and refuses an approval unless that status is connected and the mode matches the deployment. A returned pending approval means that saved-state check passed at preparation; it is not a fresh broker RPC, an executed run, or a guarantee of later execution. Do not request another reconnect from an old skipped run alone; require a current structured reconnect-required result. Does not stop, restart, replace or update the bot. Refuses overlapping runs. An explicit restart uses update_deployment_revision, including a request to restart and run immediately. If unavailable, explain the limitation; never substitute start_deployment or update_deployment_revision. For run_deployment_once, the authorization status describes approval and dispatch, not the strategy iteration. Pending approval means no strategy iteration has started. A completed action with metadata.executionResult.status=launched means launch accepted; completion and trades remain unverified. A skipped result started no new iteration. An already_recorded result is a duplicate dispatch; inspect its run_id, last_run_status and run history. A failed or unconfirmed dispatch without terminal run evidence leaves the iteration outcome unknown. Inspect run history before any new request; do not automatically retry or infer that the run failed or finished. A balance or holdings report does not verify iteration completion. Answer questions about whether the RUN finished from iteration evidence: launched means completion is unverified. Do not lead with Yes and then qualify it when only the approval completed or launch was accepted.For Codex, Claude, Cursor, and other clients without BotSpot native confirmation cards, return the exact authorizationUrl as a clickable Markdown link in your reply. Do not say a card or button was created unless the client actually rendered it. BotSpot clients may render structuredContent as a native confirmation, but a button name alone is not an approval link. A pending request is not execution; only the signed-in user may approve on the website. Report expiry and check get_deployment_action_status after approval.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| deploymentId | Yes | ||
| idempotencyKey | No |