Serverless runner fails to configure — "no permission to list datacenters" on token role
🪲type: bug
Hitting a blocker with serverless runner configuration on Rivet Cloud.
Setup:
- Rivet Cloud (not self-hosted)
- Serverless mode on Cloud Run
- RivetKit 2.0.42 (Engine - Serverless)
- Single actor type with
-
The problem:
Every Cloud Run instance that boots logs this immediately after RivetKit prints its startup banner:
This happens on every single instance, consistently. The token works fine for:
- Creating actors (PUT /actors)
- Routing gateway requests (POST /gateway/.../action/...)
- Health checks, metadata endpoints
But the serverless runner pool configuration fails often and says the token's role is missing the "list datacenters" permission.
Setup:
- Rivet Cloud (not self-hosted)
- Serverless mode on Cloud Run
- RivetKit 2.0.42 (Engine - Serverless)
- Single actor type with
crash_policy: 'destroy'noSleep: trueslotsPerRunner: 1-
requestLifespan: 2_700_000The problem:
Every Cloud Run instance that boots logs this immediately after RivetKit prints its startup banner:
This happens on every single instance, consistently. The token works fine for:
- Creating actors (PUT /actors)
- Routing gateway requests (POST /gateway/.../action/...)
- Health checks, metadata endpoints
But the serverless runner pool configuration fails often and says the token's role is missing the "list datacenters" permission.
Build and scale stateful backends. Rivet Actors is a library for long-lived processes with durable state, realtime, and scalability. Easily self-hostable and works with your infrastructure.
1,419Members
Resources
Similar Threads
Was this page helpful?
