cloro WebsiteAPI Get an API key
API Reference › Utilities › Get async status

Get async status

Read a real-time snapshot of your organization's asynchronous task queue so you can gauge load, plan capacity, and pace new submissions.

GET https://api.cloro.cloud/v1/async/status

Overview

This endpoint reports how many asynchronous tasks are waiting or in flight for the organization tied to your API key, along with how much of your concurrency allowance is currently occupied. It is a lightweight, read-only call intended for dashboards, autoscaling logic, and back-pressure decisions before you enqueue additional work.

The response also breaks queued work down by priority, letting you see whether high-priority jobs are backing up behind lower-priority ones. No request body or query parameters are required; authentication alone scopes the result to your organization.

Response fields

FieldTypeDescription
queuedTasksintegerTotal tasks currently waiting in the queue for your organization.
processingTasksintegerTasks that have left the queue and are actively being executed.
priorityBreakdownarrayPer-priority tallies of queued tasks, sorted from highest priority to lowest. Priority levels with no waiting tasks are omitted.
priorityBreakdown[].priorityintegerThe numeric priority level, where higher values are served first.
priorityBreakdown[].countintegerNumber of queued tasks sitting at this priority level.
concurrencyobjectConcurrency usage summary. May be null when this information cannot be resolved.
concurrency.usedintegerConcurrent execution slots occupied right now.
concurrency.maxintegerMaximum concurrent tasks permitted for your organization, determined by your plan.

Response example

{
  "queuedTasks": 7,
  "processingTasks": 3,
  "priorityBreakdown": [
    { "priority": 10, "count": 2 },
    { "priority": 5, "count": 4 },
    { "priority": 1, "count": 1 }
  ],
  "concurrency": {
    "used": 3,
    "max": 8
  }
}

Notes

Treat every value as a point-in-time reading; counts can shift between calls as tasks are picked up and completed. When concurrency comes back as null, fall back to queuedTasks and processingTasks for a coarse view of load rather than assuming capacity is exhausted.

If concurrency.used is at or near concurrency.max, expect newly submitted tasks to wait in the queue until a slot frees up. For questions about raising your concurrency limit, contact [email protected].