Ask Bill!

CRA Monitoring Errors

Guide to troubleshooting Servicing subscription errors

SUBSCRIPTION_NOT_FOUND

The provided subscription_id could not be found.
Common causes
  • The subscription_id was never created, or contains a typo.
  • The subscription_id belongs to a different client.
  • The subscription was already deleted.
  • The subscription_id was created in a different environment (Sandbox vs Production).
Troubleshooting steps
API error response
http code 404
{
 "error_type": "CRA_MONITORING_ERROR",
 "error_code": "SUBSCRIPTION_NOT_FOUND",
 "error_message": "no subscription found for the subscription id provided.",
 "display_message": null,
 "request_id": "HNTDNrA8F1shFEW"
}

SUBSCRIPTION_ALREADY_EXISTS

The user already has an active subscription of the requested kind.
Common causes
  • The user already has an active subscription and can hold only one of this kind at a time.
  • A create call was retried after the original call had already succeeded.
Troubleshooting steps
API error response
http code 400
{
 "error_type": "CRA_MONITORING_ERROR",
 "error_code": "SUBSCRIPTION_ALREADY_EXISTS",
 "error_message": "there already exists a subscription for the given user token.",
 "display_message": null,
 "request_id": "HNTDNrA8F1shFEW"
}

SUBSCRIPTION_LIMIT_EXCEEDED

The user has reached the maximum number of active Servicing subscriptions.
Common causes
  • The user already holds the maximum of 10 active subscriptions.
  • Subscriptions were created per report rather than reused, so unused subscriptions have accumulated on the user.
Troubleshooting steps
API error response
http code 400
{
 "error_type": "CRA_MONITORING_ERROR",
 "error_code": "SUBSCRIPTION_LIMIT_EXCEEDED",
 "error_message": "the provided user token has reached the maximum allowed number of active CRA Servicing subscriptions.",
 "display_message": null,
 "request_id": "HNTDNrA8F1shFEW"
}