Skip to main content

​
Insufficient Credits

Add credits under Settings → Credits in your workspace’s dashboard.

​
concurrency_limit_reached or cpu quota exceeded

Check your workspace limits and running containers. Stop unused deployment versions; warm containers consume capacity even without requests.

​
Unable to connect to gateway

Run beam doctor to check your connection and credentials. Try beam login to sign in again, or upgrade the CLI.

​
No module named beam

uv tool install installs an isolated CLI. Install the SDK in your project environment too:
Install your file’s top-level imports locally too. Packages added to an Image are only installed remotely.

​
cannot import name 'App' from 'beam'

App belongs to the older V1 SDK. Use V2 decorators and abstractions; see the migration guide and quickstart.

​
No space left on device

Run df -h inside the container to find the full filesystem. Remove temporary files or move persistent data to a volume or disk.

​
Deployment Active, But Requests Fail

Check logs and make sure your server listens on the configured port at 0.0.0.0 or ::. Use beam deployment wait <id> to check endpoint or ASGI readiness.

​
No URL Returned

Set a port for your web service, or call expose_port on a sandbox. Containers without ports have no public URL. Sandbox URLs are public.

​
A Command Containing Pipes Does Not Work in a Sandbox

Use sb.process.exec("sh", "-c", "first-command | second-command") for shell syntax, then .wait() for completion. See process management.

​
GPU Requested, But the Framework Cannot Use It

Run nvidia-smi, then check that your framework and CUDA versions support the GPU. See GPU acceleration.