​
Error codes

​
PCC-1002

Attempt to start agent without public api key.

Ensure you have provided a valid public API key when starting an agent. Learn more about creating and managing API keys.

​
PCC-1004

Billing credentials not set. Please set billing credentials via the Pipecat Cloud dashboard.

In order to deploy or start an agent on Pipecat Cloud, you must have valid billing credentials set up on the namespace or organization you have specified. You can set up these up via the Pipecat Cloud dashboard.

​
PCC_IMAGE_NOT_FOUND

The provided image address or tag could not be found.

Check your provided image, tag and host address to ensure they are correct.

​
PCC_IMAGE_PULL_UNAUTHORIZED

Unauthorized to pull image at given address.

If you are using a private repository, ensure you have provided valid credentials to access the repository via image pull secrets.

​
PCC_IMAGE_TOO_LARGE

Image is too large.

Ensure the image you are attempting to pull is not too large. Currently, Pipecat Cloud has no maximum image size limit, but excessively large images may cause issues when deploying agents.

​
PCC_IMAGE_PULL_RATE_LIMIT

Remote repository rate limited the pull request.

Check that your image repository is not rate limiting your pull requests. This can be caused by excessive requests to the repository, or by the repository owner setting rate limits.

​
PCC_INVALID_IMAGE_PLATFORM

Image platform is not supported.

Ensure the image you are attempting to pull is supported by Pipecat Cloud. Currently, Pipecat Cloud only supports images for the linux/arm64 platform.

​
PCC_IMAGE_PULL_UNKNOWN_ERROR

Unknown error occurred when attempting to pull the image.

If you receive this error, please contact support for further assistance.

​
PCC_UNKNOWN_ERROR

Unknown error occurred when attempting to start provided image.

Indicates an error in your image that prevent your agent from starting. Typically pcc agent logs [AGENT_NAME] will provide more information on the error.

​
PCC-AGENT-AT-CAPACITY

Service maximum instances reached

This error indicates that the maximum active sessions for your deployment have been reached. You can either increase the maximum active sessions for your deployment (max-instances), or place the end-user in a queue until a session becomes available.