Storage and the storage quota#

Applies to v0.9Last reviewed

In short

A workspace's stored files are counted in bytes and can have a storage quota. A quota only stops you starting a new take: it never refuses the copy of a take already paid for, never charges for what it refuses, and never deletes anything.

Zymcos keeps what your workspace makes. When a model finishes a take, the file is copied into Zymcos's own storage, so it stays yours and stays available after the model provider has discarded its copy. That storage is counted for your workspace, and a workspace can have a ceiling on it: a storage quota. This page says what is counted, what the quota refuses, and, just as important, what it never refuses.

What is counted#

Storage is counted per workspace, not per production, in bytes. Every file Zymcos takes into its own keeping adds to the count: the takes copied in from the model providers, script exports, and the masks made by region edits.

Identical files are counted once. If a second take is byte-for-byte the same as one your workspace already holds in the same folder, Zymcos keeps one object and points both takes at it. The second adds nothing to the count.

The quota#

A quota is a number of bytes, the same for every workspace. Where none has been set, nothing is refused: by default there is no quota. The app does not show a running total of what your workspace holds.

Where a quota is set, it is checked at one moment: when you ask for a new take. If your workspace already holds the quota or more, the take is refused, and nothing is spent.

What a quota never does#

  • It never refuses a copy. A take that was already paid for is always copied into your storage, even if that takes the workspace over its quota. A copy that failed to happen would lose a file you had paid for, because the model provider's copy expires. So the quota can only stop you starting something new. It never puts a finished take at risk.
  • It never charges for what it refuses. The check comes before any money is reserved, so a take refused for storage costs nothing.
  • It never deletes anything. Being over the quota does not remove, hide or archive a file.

What a refusal looks like#

In an autopilot run, the step that could not start says:

This workspace's storage is full, so this step was not started.

On a take proposed on a card in CODA, the card says That did not go through, and nothing was spent, and offers to try again or to ask CODA for a new proposal. Trying again with the workspace still at its quota gets the same answer.

Making room#

Space comes back only when a file's bytes are removed. Withdrawing a file is not that: it takes the file out of circulation but keeps it, so it still counts.

Erasing removes the bytes, and it is refused while the file is referenced, committed or delivered. It is done by support, not by a button; see Your files, Taking a file out of circulation. When the erased file's bytes have left, the space it used is released. A file that was identical to another one held only a share of a single object and releases nothing.

If you keep running into the quota, tell support.