UTXO stuck in jar due to too many tries

[Surenos18]

First of all understand I am a not tech savvy and struggle to understand code and command prompt issues.
I had 3 successful coin collaborations using Jam within my own node from Umbrel.
On the 4th transaction I started a collaboration and when I came back to the screen, it looked like the collaboration was not happening as the screen was open for sending. I made another 2 attempts with the same results. After the 3rd attempt, there was an error message on my jar stating that due to too many attempts, the utxo could not be used again. So it appears the utxo is stuck in the jar and I don't know how to get it out. Can someone explain what is going on and if this can be rectified?

[Surenos18]

I was able to retrieve the UTXO by transferring out of JAM in a non-collaborative transaction. I'm still curious why when I attempted the collaborative coinjoin, they did not go through?

[theborakompanioni]

Hey @Surenos18!

It is not easy to tell why this happened. It seemed you could not successfully use that UTXO in a collaborative transaction. Three attempts (by default – should not be changed) are possible before you have to use different UTXOs. As you described, the situation can be resolved with a non-collaborative spend or (as far as I understand - not verified) by creating a new UTXO in the jar (amounting to at least 20% of the total sending amount of the collaborative transaction).

From DOCS/SOURCING-COMMITMENTS.md:

As an example, if you send to 3 addresses instead of 1, you will then have 9 commitments available - effectively 9 tries at doing the first transaction, instead of only 3 tries if you send the coins to one address.