Errors

quota_exceeded

The account has used up a quota, such as publishes per 24 hours, stored release bytes or concurrent test rooms.


Kind	`disko` command error
`disko` exit code	5 (conflict)

disko-master and the registry check the account's quotas before they accept work. When one is used up, the command fails with quota_exceeded and exits with code 5. The message says which quota it was:

disko publish: 100 publishes per account in any rolling 24 hours, and 2 GiB of stored release archives per account.
disko dev: at most two test rooms per account at a time, by default.

Fix

Publishes per 24 hours: wait. The window is rolling, so publishing works again once earlier publishes are older than 24 hours. Check changes with disko publish --dry-run instead of publishing intermediate builds.
Stored release bytes: releases are never deleted, and deprecating one frees nothing, so every published archive counts for good. Keep releases small, or ask disko support for a higher quota.
Test rooms: stop another disko dev session. A stopped session frees its slot within seconds; one that was killed frees it when its room's lease runs out, about 30 seconds later.

A failed publish never uses up the version, so you can publish the same version once the quota allows it.