Canceling Your Automation Task

Why Cancel?

Canceling an active task stops it running after the current cycle ends. A cancelled pending task never runs. To stop an active task at once, use stop-tasks (below).

Useful when:

• Task logic is no longer needed.
• You made a mistake in the task parameters.
• You want to avoid draining your wallet from recurring executions.

supra move automation cancel \
  --task-index <TASK_INDEX> \
  --rpc-url <RPC_URL>

supra move automation cancel \
  --task-index 347 \
  --rpc-url https://rpc-testnet.supra.com

After Canceling

What happens depends on the state of the task when you cancel it:

• Pending task (registered, not yet active): the task is removed immediately and half of the deposit is refunded. The registration fee is not refunded.
• Active task: the task is marked as cancelled, and it stays in the registry until the current cycle ends. It can still execute until then, and the automation fee already charged for the current cycle is not refunded. At the cycle boundary the task is removed, no further automation fee is charged, and the full deposit is returned.

The cancellation emits a TaskCancelledV2 event. A task that is already cancelled cannot be cancelled again (EALREADY_CANCELLED).

Gas fees are charged only for executions, so a removed task incurs no further gas fees.

Stopping a Task Immediately

supra move automation stop-tasks removes tasks at once instead of waiting for the end of the cycle. It takes one or more task indexes:

supra move automation stop-tasks \
  --task-indexes <TASK_INDEX_1> <TASK_INDEX_2> \
  --rpc-url <RPC_URL>

For each stopped task the owner receives:

• the full deposit if the task is active or cancelled, or half of it if the task is pending;
• half of the automation fee for the time that remains in the current cycle, if the task is active or cancelled.

The registration fee is not refunded. The transaction aborts with EUNAUTHORIZED_TASK_OWNER if any of the listed tasks belongs to another account, and with EEMPTY_TASK_INDEXES if the list is empty. The refunds are reported in a TasksStoppedV2 event.

Post-Cancel: Sanity Check

• Visit SupraScan 
• Search your deployer address
• Navigate to the Tasks tab or check your function call history
• Confirm that the automated function is no longer executing once the cycle in which you cancelled has ended