---
title: "Query workspace daily maximum concurrent test runs"
method: GET
path: "/workspaces/{workspace_id}/reports/usage/maxTestRunConcurrency"
tags: ["Reporting"]
---

# Query workspace daily maximum concurrent test runs

`GET /workspaces/{workspace_id}/reports/usage/maxTestRunConcurrency`

Retrieve the daily maximum number of simultaneously executing test runs in an active workspace, along with the workspace's configured test run concurrency limit for the same test type. The reported `max_test_run_concurrency` is computed as the maximum number of runs executing at any single instant during the day — not an average, not a count of runs started. If ten runs start and finish within the same minute but a different run was also executing for that minute, the maximum for that minute is eleven.

Use this endpoint to track how close a workspace is running to its purchased concurrency capacity, decide when to request a limit increase, identify load bursts, or correlate peak usage with customer-side deployment or traffic patterns. Compare the `max_test_run_concurrency` values against `configured_test_run_concurrency_limit` to see headroom.

Data is pre-aggregated from billable events by a background job that runs every 12 hours, so values for the current calendar day may be incomplete until the next aggregation cycle finishes. Time range cannot exceed 90 days. If `start_time` and `end_time` are both omitted, the endpoint returns the last 90 completed days ending at the start of the current UTC day.

The `configured_test_run_concurrency_limit` is resolved against the requested `test_type`. For `browser` (the default when unspecified), it is the sum of the workspace's Linux, macOS, and Windows browser quotas. For `api`, `mobile`, or `performance`, it is the single numeric quota for that resource. A workspace with no configured quota for a given test type returns `configured_test_run_concurrency_limit: 0`.

## Path parameters

- `workspace_id` string, required

## Query parameters

- `start_time` integer
- `end_time` integer
- `test_type` 'api' | 'browser' | 'mobile' | 'performance'

## Response `200`

Daily maximum concurrent test run data for the workspace

- WorkspaceMaxTestRunConcurrencyResponse — Daily maximum concurrent test run data for a single workspace, along with the workspace's configured test run concurrency limit for comparison. On the workspace endpoint this is the top-level response object. On the account endpoint it appears once per workspace within the `workspaces` array.
  - `workspace_id` string — Identifier of the workspace this block describes. Always populated with this block's workspace identifier.
  - `start_time` integer — Inclusive start of the queried time range as Unix epoch milliseconds, echoed from the request (or the default-derived value when the request omits it).
  - `end_time` integer — Exclusive end of the queried time range as Unix epoch milliseconds, echoed from the request (or the default-derived value when the request omits it).
  - `configured_test_run_concurrency_limit` integer — The workspace's configured maximum concurrent test runs for the requested `test_type` at the time of the query. For `browser`, this is the sum of the workspace's Linux, macOS, and Windows browser quotas. For `api`, `mobile`, or `performance`, this is the single numeric quota for that resource. Returns `0` if the workspace has no configured quota for the requested test type. Compare `max_test_run_concurrency` against this value to see how close the workspace is running to its purchased capacity.
  - `time_buckets` UsageMaxTestRunConcurrencyBucket[] — Daily-only time buckets for this endpoint. One entry per UTC calendar day in the queried range that had any runs of the requested test type. Ordered by `bucket_start_time` ascending. Days with no runs are omitted.
    - `bucket_start_time` integer — Inclusive start of the day (midnight UTC) as Unix epoch milliseconds. Maximum test run concurrency is always computed against UTC calendar days.
    - `bucket_end_time` integer — Exclusive end of the day (midnight UTC of the next day) as Unix epoch milliseconds. Always 24 hours after `bucket_start_time`.
    - `max_test_run_concurrency` integer — Maximum number of test runs of the queried `test_type` that were executing simultaneously at any instant during this day. Computed via a sweep-line over run start/end times in the underlying billable events data.

## Other responses

- `400` — Invalid or missing parameter
- `401` — User not authenticated
- `403` — User not authorized
- `default` — Unknown error

---

[API](https://skmtc.net/mabl/apis/mabl-api.md) · [All operations](https://skmtc.net/mabl/apis/mabl-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/mabl/mabl-api/revisions/d0fc0114da66/schema)