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.