Background Tasks - API Documentation
Overview
Tasks endpoints manage asynchronous jobs stored in the task manager (create/rerun/check/list/delete task records).
Quick Links
- Tasks - Update Task -
/i/tasks/update - Tasks - Edit Task -
/i/tasks/edit - Tasks - Name Task -
/i/tasks/name - Tasks - Delete Task -
/i/tasks/delete - Tasks - Read All Tasks -
/o/tasks/all - Tasks - Count Tasks -
/o/tasks/count - Tasks - List Tasks -
/o/tasks/list - Tasks - Read Task -
/o/tasks/task - Tasks - Check Task Status -
/o/tasks/check
Data Model
| Collection | Purpose |
|---|---|
countly.members | Member identity/permissions used by task endpoint read/write validators and visibility filters. |
countly.long_tasks | Stores task metadata, status, request payload, and optional inline result metadata. |
countly_fs.task_results | Stores large/binary task results when GridFS-backed task storage is used. |
Behavior Notes
- Task execution can be synchronous to caller (status response) but usually results are asynchronous.
- Some endpoints return wrapped
resultpayloads, while others return raw objects. - Visibility rules combine task ownership (
creator) and global-task visibility.
Related Endpoints
Last Updated
2026-02-17