409 screening_cap_exceeded - NoResponse docs

{
  "type": "https://docs.noresponse.org/problems/screening-cap-exceeded",
  "title": "Screening cap exceeded",
  "status": 409,
  "detail": "The screening's estimated spend exceeds what the environment's daily screening cap has left today. Raise screening_daily_cap in the environment's settings, screen fewer people or platforms, or wait for the next UTC day.",
  "code": "screening_cap_exceeded",
  "request_id": "5e8be3a91fde9499f7ce48ae66290895"
}

{
  "type": "https://docs.noresponse.org/problems/screening-cap-exceeded",
  "title": "Screening cap exceeded",
  "status": 409,
  "detail": "The screening's estimated spend exceeds what the environment's daily screening cap has left today. Raise screening_daily_cap in the environment's settings, screen fewer people or platforms, or wait for the next UTC day.",
  "code": "screening_cap_exceeded",
  "request_id": "5e8be3a91fde9499f7ce48ae66290895"
}

HTTP 409 Not retryable

What to do

Raise screening_daily_cap in the settings of the environment, select fewer people or platforms, or start the screening on the next UTC day.

In the SDKs

The Node and Python SDKs raise ConflictError. The Go SDK returns *apierrors.ConflictError, which you match with errors.As.

{
  "type": "https://docs.noresponse.org/problems/screening-cap-exceeded",
  "title": "Screening cap exceeded",
  "status": 409,
  "detail": "The screening's estimated spend exceeds what the environment's daily screening cap has left today. Raise screening_daily_cap in the environment's settings, screen fewer people or platforms, or wait for the next UTC day.",
  "code": "screening_cap_exceeded",
  "request_id": "5e8be3a91fde9499f7ce48ae66290895"
}

Every error has this shape. Errors and limits lists every code.