ResourceSync Busy

[porochickenrye]

I have been trying for hours but am still not able to get resource sync to work. When it works, it delete my resources such the server even though I have managed set to false. Anyway, when every sync occurs, I always see a ResourceSync error in the logs of the sync tasks

Update ResourceSyncs
Stage 6 of 6|
0.0 seconds
stderr
running updates on ResourceSyncs
ERROR: failed to update config on ResourceSync 'docker-compose-sync' | ResourceSync busy

What is causing this? This is a brand new deployment so there isn't really anything that could be locking up ResourceSync as far as I know of.

[mbecker20]

It looks like the ResourceSync is trying to update its own config during execution, which is failing because the sync is currently running. To resolve it, you can modify the resource sync config in toml to match what is in UI. With managed mode, committing to sync would also resolve this issue.

[porochickenrye]

Thanks! I’ll try it tonight. If I start with a blank slate and just a Git provider, would the initial sync be successful if my TOML config file is empty?

Also, for the managed mode, is it intentional that the Delete Resources option is also enabled when managed mode is turned on? When I tried yesterday, that seemed to be the case. Is there a way to keep managed mode on without resource deletion?

[porochickenrye]

Never mind. Please ignore my earlier questions.
I never saw the Pending tab and the Commit Changes button. In dark mode, they were totally just text to me. I didn't think to myself to commit changes to the sync would go through. Maybe a minor UX enhancement item?