What deleting or disabling affects
Fibe is built to protect you from foot-guns. The actions that could take other things down with them are blocked until you've cleared the dependency, and the few that actually delete data say so first. Here's exactly what each action touches.
Subscription cleanup release scope
The delayed-cancellation correction is deployed to staging, next.fibe.live, and has not yet been promoted to fibe.gg. See the billing release note for its scope. Cancellation, stopping runtime, and retention cleanup are separate steps; a database record surviving does not by itself prove that its runtime data has been recovered.
At a glance
| You do this… | …and this happens | Data |
|---|---|---|
| Disable a Marquee | New launches, schedules, and triggered runs are blocked, and automatic maintenance stops. Running Playgrounds and live Genie chats keep running: self-hosted or platform-managed. (It's non-payment, not disabling, that pauses a platform-managed Marquee's environments: see Billing.) | Kept |
| Delete a Marquee | Blocked while Playgrounds or Tricks are attached: move or remove them first. Genie chat sessions on the Marquee are removed along with it automatically and do not block deletion. A Marquee with unresolved billing incidents also can't be deleted; settle the balance first. A self-hosted host machine is never touched. | Kept |
| Stop a Genie | Runtime off, workspace kept. Restart resumes. | Kept |
| Clean up / purge a Genie | Runtime down and the workspace deleted. | Deleted |
| Delete an Agent | Its Genie chats are cleaned up. Playgrounds it was attached to survive and lose only the Agent link. | Chat workspace deleted; Playgrounds kept |
| Rotate / revoke an API key | Running Genies that used it redeploy to pick up the change. Nothing is deleted. | Kept |
| Delete a Prop | Blocked while a Playspec still references it. A Template imported from the Prop is not a blocker: it keeps working but quietly loses its source connection, so detach or re-point such Templates first. | n/a |
| Cancel a subscription | A platform-managed Marquee tied to it survives as long as it stays funded. | Kept |
| Expire a Playground | Clean → destroyed (containers, named volumes unless persistence is on, and the record). Uncommitted changes → parked, not destroyed. | Volume kept only if persistence is on |
| Destroy a Playground | Always tears down containers, volumes (unless persistence is on), and the record: uncommitted changes included. Commit or push your work before destroying. | Volume kept only if persistence is on |
What happens to named volumes
Routine lifecycle actions never remove named volumes. During teardown, the Playspec's Stateful (Persist Volumes) setting decides:
| Action | Named volumes |
|---|---|
| Stop | Always kept |
| Rollout / restart | Always kept |
| Destroy or expiration | Kept only if Stateful (Persist Volumes) is on |
The three rules behind the table
- You can't pull the ground out from under a running thing. A Marquee won't delete while Playgrounds or Tricks live on it, and a Prop won't delete while a Playspec points at it. Clear the dependency first: the product lists what's in the way.
- Disabling is reversible; deleting and cleaning up are not. Re-enabling a Marquee restores its services. Prop disablement is internal; users can delete a Prop only after removing Playspec references. Clean up / purge permanently deletes a runtime's stored data after confirmation.
- Your configuration outlives any runtime. Agent settings, mounted files, credentials, Templates, and your Wallet are account-level. Stopping, restarting, or cleaning up a runtime never touches them.
See also
- Agents: Stop vs. clean up: what a Genie keeps vs. deletes.
- Marquees: Removing a Marquee: the safe decommission order.
- Billing: When your balance runs low: disabling for non-payment.
- Playgrounds: Data durability: what survives a restart.
- What Fibe recovers on its own: transient states that aren't problems.