Skip to main content

Plan Not Found

plan_not_found422

Validation · Plan reactivation only

Your cancelled plan could not be matched to a current Asterwise plan, so it could not be resumed. Contact support.

What this means​

When you resume a cancelled plan, we look up which Asterwise plan your Dodo subscription is for. This error means that lookup found no match, so the plan was not resumed and nothing changed. The response is HTTP 422.

When you'll see this​

  • You clicked Resume plan on a cancelled subscription whose product is not one of the current Asterwise plans, for example a plan that is no longer sold.

It is not returned when choosing a plan to buy: an unknown plan name there gets validation_error with the list of valid plans.

Learn more about how this works

Each paid subscription is stored with the Dodo product it was bought as. Resuming needs that product to map to a current plan (Builder, Launch or Scale, monthly or yearly) so the right limits apply. When it does not map, we stop rather than guess which plan to give you.

Example response​

{
"success": false,
"error": "plan_not_found",
"message": "The specified plan does not exist.",
"details": [],
"retry_after": null,
"doc_url": "https://docs.asterwise.com/reference/errors/plan_not_found/",
"request_id": "req_01HXYZABCDEFGH",
"timestamp": "2026-05-25T12:34:56Z"
}
NEW TO APIS?
Quick fix
  1. Email [email protected] with the request_id from the error; support can match the subscription to the right plan.
  2. Or let the cancelled plan run out and subscribe to a current plan from asterwise.com/dashboard.
PRODUCTION ENGINEER
Recovery pattern

Only the dashboard receives this error: resuming a plan needs a dashboard sign-in, and an API key sent to that endpoint gets session_required instead. Code that calls the API with a key never sees plan_not_found.

Production handler​

No code example provided.

Avoid this error by​

  • Nothing on your side; this is a mapping we fix for you.