Per-customer execution concurrency controls

You can now set per-customer execution concurrency limits to prevent a single customer's high-volume integrations from consuming a disproportionate share of your organization's execution capacity.

When a customer reaches their limit, additional execution attempts return a 429 "too many requests" response.

You can configure limits from the Prismatic web app, via the GraphQL API, or via embedded JWT claims. You can also set up a Customer Concurrency Threshold Warning alert monitor to be notified when any customer approaches their limit.

This feature is available on Enterprise plans. See per-customer execution concurrency for more information.