// Background task runs — list, inspect, retry. Use this to debug async failures from doc +upload, publish, etc.
Layer 3 raw HTTP: any endpoint not yet covered by a flow or resource verb.
Manage Droploft documents (drops): upload, list, get, content, share, publish, delete.
Lofts: types, switching, listing, member operations.
Droploft v2 CLI: authentication, configuration, profiles, and patterns shared across all domains.
Workspaces: switching, listing, members, navigation tree.
| name | droploft-tasks |
| version | 0.2.0 |
| description | Background task runs — list, inspect, retry. Use this to debug async failures from doc +upload, publish, etc. |
| metadata | {"requires":{"bins":["droploft"],"skills":["droploft-shared"]},"cliHelp":"droploft tasks --help"} |
Async work runs as task runs. The most common producer is publish/optimize, kicked off by doc +upload or documents publish. Each row tracks status, attempts, and error_message.
pending → running → success | failed | cancelled
(success is the canonical terminal state; v1 spec called it succeeded — v2 uses success. The CLI accepts both when polling.)
droploft tasks list # most recent first
droploft tasks list --format table # human-readable
droploft tasks get <task-id> # one row
droploft tasks retry <task-id> # re-enqueue a failed task
droploft tasks list --format json --jq '.[] | select(.status=="failed")' | head
--no-waitdoc +upload polls automatically. If you used --no-wait, follow up:
TASK_ID=$(droploft documents publish <doc-id> --format json --jq '.data.task_id')
while true; do
STATUS=$(droploft tasks get "$TASK_ID" --format json --jq '.data.status')
case "$STATUS" in success|failed|cancelled) break;; esac
sleep 3
done
echo "final: $STATUS"
not_found (exit 4) — the task belongs to another user, or doesn't exist.tasks retry on a non-failed row returns 409 conflict.