A node change is refused when you're not the engine owner, when an earlier change is still settling, or when it would leave the engine too fragile or unpaid; the console shows the reason next to the button or in a notice.
- Not the owner. Admins and developers see "Only the engine owner can add, remove or replace nodes." Ask the owner.
- A node is still syncing. A node added or swapped in recently is still catching up (about 15 minutes, longer if it is behind). Wait until the time shown. This also holds back Start migration.
- A change is already running. Wait for the Node change in progress banner to clear, or for a class migration to finish (or stop it with Stop migration).
- At least 4 nodes. An engine must keep 4 nodes. Add one before removing one.
- No spare node to lose. Removal is refused while another node is down or a new one is still catching up. Bring the down node back, or remove that one instead.
- Balance too low. The balance must cover a new node's first 7 days. Add at least the amount shown, then try again.
- Engine halted, being deleted or shutting down. A halted engine needs funds before its nodes can change. One whose balance ran out, or that is shutting down, can't change nodes any more.
- "This engine has no balance to pay for a node change": its nodes can't be changed from the console.
- Greyed-out catalog rows. A node on the same physical machine as one of yours, or whose address isn't published, can't join: one hardware failure could hit both.
- No Replace node on an offline node. It appears only after 15 minutes offline, and not while so many nodes are down that the engine can't finalize blocks.
- Upgrade class shows a warning. The engine is already on the top class, or on a class that can't be upgraded.
- Nothing to pick. "No additional nodes available at the moment." or No replacement available means every fitting node is taken. Try again later.
Good to know
- Changes go one at a time: one node added, removed or swapped per change.