Collection cannot be disabled or removed while authority transfer fences mutations

[callumalpass]

Expected behavior

A local collection can be disabled or removed from mdbase Connect so that its folder can be selected for a different hosted collection.

Actual behavior

Disabling or removing the collection fails with:

AgentControlError: Collection authority transfer … is fencing mutations

The collection remains configured, preventing reuse of the same local folder.

Steps reported

1. Open a locally configured collection in the Linux desktop application installed from the RPM package, or in the browser interface.
2. Attempt to disable or remove the collection.
3. Observe that the operation fails because an authority transfer is fencing mutations.
4. Revoking the computer does not clear the condition.

The affected collection was used with TaskNotes. No application version was supplied. Reproduction is still required; this report has not yet been independently reproduced.

Reported via support email; reporter identity withheld.

[bepolymathe]

Hi @callumalpass

I have a similar problem but with a slightly different error message. I first set up a collection "on my computer" send back to my folder "Tasks" (where it creates all my notes with Tasknotes). I then created a collection "hosted by mdbase" to enjoy Tasknotes on mobile. But I can't select the same "Tasks" folder for synchronization. I have the following error message:

Error invoking remote method 'connect:mirrors:connect': AgentControlError: Mirror folder overlaps a computer-owned collection.

If I then try to disable or delete the collection "on my computer", I have the following error message:

Error invoking remote method 'connect:collections:remove': AgentControlError: Collection transfer da98010b-204a-4c8a-9dcb-8535aeed7974 is fencing mutations

I also tried to transfer the local collection to the hosted collection but it didn’t work either.