Operations
Disable vs Delete
When to disable a Function / App / Skill / Plugin, and when to actually delete.
Harbor distinguishes between two lifecycle actions.
| Action | What it does | Reversible? | Use when |
|---|---|---|---|
| Disable | Stops accepting new invocations. Existing runs / history preserved. | Yes — re-enable any time | The thing is broken / deprecated / temporarily off |
| Delete | Removes the row + future invocations + (most) history. | No — gone for good | The thing was a typo / test artifact / never should have existed |
What disable does, by resource
| Resource | Disable effect |
|---|---|
| Plugin source | Tools stop being callable; OAuth token kept; can reconnect |
| Skill | Agent host stops loading it (it's not in the skill feed) |
| Function | New SDK/dashboard invocations return 410; running runs finish |
Function @vN | Same as above, scoped to one version |
| App | Route returns 404; backing Function still callable directly |
| Workspace member | Can't sign in to the workspace; their owned resources unchanged |
What delete does, by resource
| Resource | Delete effect |
|---|---|
| Plugin source | Source row gone, credentials wiped, traces retained |
| Skill | File gone; agent forgets |
| Function | All @vN rows gone; traces retained (orphaned) |
| App | Route + manifest gone; backing Function unchanged |
| Workspace member | Membership row gone; their owned skills/functions transferred to admin |
| Workspace | Everything. Plugins, skills, functions, apps, traces, artifacts. |
Workspace delete is forever
Deleting a workspace is one-click but immediate and irreversible. Traces, artifacts, billing history — all gone. Owners only. Confirm twice.
The "soft disable" pattern
For Functions and Apps you suspect you'll need again, the pattern is:
- Mark the description as "DEPRECATED" so it sorts to the bottom
- Disable the version(s)
- Leave it for a sprint
- If nothing breaks, delete
For Plugins you suspect you'll need again:
- Disconnect (keeps credentials)
- Leave for a quarter
- If nothing breaks, remove
Traces & artifacts retention
Traces are retained per-plan even when the source resource is deleted
(orphaned traces are reachable via run ID). Artifacts (orbit.storage)
live until you delete them or storage retention expires.
| Plan | Trace retention | Artifact retention |
|---|---|---|
| Hobby | 7 days | 30 days |
| Individual | 30 days | 90 days |
| Team | 90 days | 365 days |
| Enterprise | 1 year+ | Custom |
Where to go next
- Versioning & pinning — rollback is the safer alternative to delete.
- Observability — finding orphan traces.