The Fabric capacity assigned to this workspace is exhausted and cannot create another Rayfin item.
Pass a workspace with available capacity using --workspace-id <id>, or pass --capacity-id <id>.
--capacity-id must be a GUID.
Copy the Fabric capacity GUID from the Fabric portal.
--workspace-id and --capacity-id cannot be used together.
Remove one option so Rayfin resolves either the workspace or the capacity.
RAYFIN_WORKSPACE_ID and --capacity-id cannot be used together.
Unset RAYFIN_WORKSPACE_ID or remove --capacity-id.
No workspace targeting context. Pass --workspace <name> (or --workspace-id <id> / --workspace-uri <url>), or run \rayfin up` once interactively to record a deployment.`
Provide a workspace target for non-interactive deployment.
Multiple premium Fabric capacities are available and require interactive selection.
Run interactively or pass --capacity-id <id>.
Provisioning and assigning Fabric trial capacity to workspace
Run with --yes, pass --capacity-id, or ask an admin to assign existing capacity.
Workspace Admin permission is required to assign capacity to
Ask a workspace Admin to assign capacity or promote your role.
Fabric trials are disabled for this tenant.
Ask the tenant admin to enable trials or deploy to a workspace that already has capacity.
Fabric did not finish the workspace capacity assignment within
Compressed package size (...) exceeds the 100 MB limit.
Exclude large assets or source maps, then redeploy static content.
Static hosting is enabled but services.staticHosting.assetAccess is not set in rayfin.yml
Add assetAccess: protected or assetAccess: public. Non-interactive rayfin up defaults a missing posture to protected and writes it to rayfin.yml. New in 1.35.1
services.staticHosting.assetAccess in rayfin.yml must be protected or public
Fix the value or the environment variable that resolves it.
Static hosting requires an explicit access posture. Set 'services.staticHosting.assetAccess' to 'protected' to require Fabric sign-in or 'public' to serve anyone with the link, then deploy again.
Add the access posture and redeploy.
Invalid static hosting posture: 'services.staticHosting.embedded.only: true' cannot be combined with 'services.staticHosting.assetAccess: public' because an embedded app has no standalone surface to make public.
Use assetAccess: protected or set embedded.only: false.
The static-hosting access posture has not been recorded. Run 'rayfin up' to record 'services.staticHosting.assetAccess' before trying again.
Review operations and use --force only when the data loss is expected.
GraphQL Internal server error after deploy
Add explicit max values to every @text() field, then apply the schema.
PromptDiagnose a failed Rayfin deployment
Use the exact error text from my failed `npx rayfin up` or `npx rayfin up status` run to fix the deployment. Re-run with `--verbose` if needed. Check workspace targeting, capacity readiness, `services.staticHosting.assetAccess`, static archive size, and schema configuration. Do not pass `--force` unless the destructive schema operations are expected.
The CLI error strings above come from the 1.36.2 package files dist/errors.js, dist/commands/capacity-options.js, dist/workflows/fabric-readiness/steps/*.js, dist/workflows/up/steps/ensure-static-hosting-posture.js, and dist/services/runtime-settings/errors.js.