Errors

P: Platform

Every P error code: what it means, when it happens and how to fix it.

7 codes. Each one is part of an error answer as code; type is the stable name that scripts branch on. The CLI shows the code at the end of its message, for example (code: P01). Words in braces, such as {name}, are filled in with the actual value.

P01

internal_error · HTTP 500

Something went wrong on our side. (code: P01)

When it happens. An unexpected failure that we treat as a bug. It is logged with your request ID, which tells us exactly what happened.

How to fix it. Try again. If it keeps happening, contact support with the request ID.

Retry. No. Retrying the same request gives the same answer.

P02

invalid_request · HTTP 400

That request isn't valid: {detail}. (code: P02)

When it happens. The request body was not valid JSON or a general parameter was invalid.

How to fix it. Correct the request and send it again.

Retry. No. Retrying the same request gives the same answer.

P03

payload_too_large · HTTP 413

That request is too large. (code: P03)

When it happens. The request body is larger than this endpoint accepts.

How to fix it. Send a smaller request.

Retry. No. Retrying the same request gives the same answer.

P04

not_found · HTTP 404

This address doesn't exist. (code: P04)

When it happens. The request went to an API address that does not exist.

How to fix it. Check the address.

In the CLI. Check the address, or update the kiste command-line tool with kiste update.

Retry. No. Retrying the same request gives the same answer.

P05

method_not_allowed · HTTP 405

This address doesn't accept that kind of request. (code: P05)

When it happens. The request used an HTTP method the address does not support.

How to fix it. Check the request method.

Retry. No. Retrying the same request gives the same answer.

P07

shutting_down · HTTP 503

The compute service is restarting. (code: P07)

When it happens. The computer that runs this Kiste is restarting its service; your Kisten keep running.

How to fix it. Try again in a few seconds.

Retry. Yes, with backoff: wait a moment and try again, waiting longer each time.

P13

api_token_activation_failed · HTTP 503

The new API key couldn't be activated. (code: P13)

When it happens. The API key was created but kiste.run could not activate it.

How to fix it. Revoke it and create a new one.

Retry. No. Retrying the same request gives the same answer.

On this page