Deleting things

Orbi does not block deletion. If an agent could not be deleted while three flows used it, you would have to open all three flows and pull the card out first. Instead Orbi shows you what will change, and you make the call.

#The impact list in the confirmation

When you press delete, Orbi scans where that thing is used and lists it line by line in the confirmation. The confirm button stays disabled until the scan finishes, so the warning is not skipped past.

The numbers are not estimates. Every line counts a place the deletion will actually touch, and the first few names are listed too, so you get the answer to "which three flows", not just "three flows". If it is used nowhere, it says that.

#Deleting an agent

What happens	Detail
Flow cards go with it	Wherever the agent sits on a canvas, that card and its wires are removed. The flow itself stays and keeps running.
Tasks are left unassigned	Tasks assigned to the agent are not deleted; they stay on the board without an owner.
Conversations are deleted	Your one-to-one conversations with the agent go, along with their history.
Agent columns lose their agent	If a collection column had this agent filling it in, the column and its data stay; the column is just no longer tied to an agent.
Assignment triggers pause	If a "run when assigned to this agent" trigger narrowed to only this agent, that trigger is paused.
Access tokens stop working	If the agent connected from your own device (see Coding agent), its connection is cut.

#Deleting a flow

The canvas, the triggers and the run history go together. Tasks the flow opened are not deleted; they stay on the board.

The one thing worth watching is the incoming webhook address: if an outside system posts to the flow, that address dies with it and the sender starts getting errors. The confirmation calls this out separately when such an address exists.

#Deleting a collection

Records, fields and share links go together. Two more side effects, both listed in the confirmation:

• Relation fields in other collections lose their target. If another collection's records linked to this one, that link no longer points anywhere. The field stays, its target is cleared — you need to pick a new one.
• Flow triggers watching this collection are paused. A "run when a record is added here" trigger stops when the collection it watched is gone.

#Deleting a connection

Agents that used the connection lose access to that service; flow triggers that polled it are left without a connection and show as "connection removed" on the flow screen. The triggers are not deleted — you can pick another connection.

#Deleting a board

A board is only where tasks live. Deleting it takes its tasks and nothing else; the rest of the space stays. The last board of a space cannot be deleted. The confirmation counts what changes:

What happens	Details
Tasks are deleted	The board's tasks are deleted permanently, with their comments and task chats. This part cannot be undone.
Content stays	Collections, files, folders, flows, conversations and calendar events are not deleted. They stay in their space.
Flows that open tasks lose their board	Flows that open their tasks on this board are left without a target board. The confirmation lists them by name.
Triggers watching the board pause	A trigger that listens only to this board's tasks is paused. The reason is below.
Webhook filters narrow	The board is removed from webhook board filters. A webhook with no board left is paused and the admins are told.

#Why a trigger gets paused

A trigger's narrowing is what says when it should run: "only when assigned to this agent", or "only when written to this collection". If the only thing in the narrowing is deleted, an empty narrowing is left behind — and in Orbi an empty narrowing means "run every time".

Orbi will not leave the trigger running in that state. If it did, deleting one agent would quietly produce a flow that reacts to every task — something you never asked for happening without you ever saying you wanted it. The trigger is paused; you decide what you want and turn it back on.

#What is not deleted

Some traces stay on purpose, because they are the answer to "what happened":

• Steps in the run history. Work a deleted agent did earlier stays readable in the run history; its name is kept in that record.
• Task checklists. A step opened by mistake is not deleted, it is marked as an error (see Tasks).
• The activity timeline. The record of who did what is not cleared by a deletion (see Activity).