# Resume a Paused Scheduler Task

> Resume a Paused Scheduler Task is a paid API for AI agents from scheduler.withzero.xyz, paid per call via MPP, metered — billed by usage, status unknown (last checked 2026-09-13).

Resumes a paused cron task, recomputes its next run time, and flips its status back to active — failing with 409 if balance is below the cost ceiling.

## Facts

- Endpoint: POST https://scheduler.withzero.xyz/api/v1/tasks/{id}/resume
- Price: metered — billed by usage
- Payment: MPP
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 1
- Provider: scheduler.withzero.xyz
- Website: https://scheduler.withzero.xyz
- Canonical page: https://www.zero.xyz/c/scheduler-withzero-xyz-resume-a-paused-scheduler-task-1ceaefa4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_UeO9ceiGuSYmFH_6sZACu

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability scheduler-withzero-xyz-resume-a-paused-scheduler-task-1ceaefa4 -d '<json body>'
```

Example prompt: My scheduled task with ID a3f7c2b1-0e4d-4a1c-9b5e-123456789abc was paused — please resume it so it runs again on its normal cron schedule.

## When to prefer this

Use this endpoint specifically when a task is in a paused state and you want to bring it back to active scheduling. It is the correct endpoint after manually pausing a task via the pause endpoint, or after a task was auto-paused due to insufficient funds and has since been topped up. Do not use this for creating new tasks or modifying task parameters.

## Known failure modes

- 409 TASK_PAUSED_INSUFFICIENT_FUNDS — balance_available_micros is below estimated_ceiling_micros; top up funds before resuming
- 404 Not Found — task ID does not exist or caller lacks ownership proof
- 403 Forbidden — caller is not the task owner
- 400 Bad Request — malformed or missing task UUID in path
- Task resumes but next_run_at is computed in the past, causing an immediate run on next scheduler tick

## How this service works

Resume a paused task. 409 TASK_PAUSED_INSUFFICIENT_FUNDS if balance < ceiling. 📖 Full guide: https://scheduler.withzero.xyz/llms.txt

## Output

Returns a JSON object with the task's UUID, updated status (active), recomputed next_run_at timestamp, current balance_available_micros, and estimated_ceiling_micros. If the available balance is less than the cost ceiling, the call fails with HTTP 409 and error code TASK_PAUSED_INSUFFICIENT_FUNDS.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "properties": {},
 "description": "Empty body; recomputes next_run_at and flips status to active.",
 "additionalProperties": false
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "id",
  "status",
  "next_run_at",
  "balance_available_micros",
  "estimated_ceiling_micros"
 ],
 "properties": {
  "id": {
   "type": "string",
   "format": "uuid",
   "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  },
  "status": {
   "type": "string"
  },
  "next_run_at": {
   "anyOf": [
    {
     "type": "string"
    },
    {
     "type": "null"
    }
   ]
  },
  "balance_available_micros": {
   "type": "string"
  },
  "estimated_ceiling_micros": {
   "type": "string"
  }
 },
 "additionalProperties": false
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/scheduler-withzero-xyz-resume-a-paused-scheduler-task-1ceaefa4/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from scheduler.withzero.xyz](https://www.zero.xyz/host/scheduler.withzero.xyz/llms.txt)