Jeez... I could have looped infinitely without your suggestion... Thanks, it does work indeed, and it saves my evening...

3 weeks ago and no reply ? same question here....

Yep I have this issue too... My post, a few minute ago : https://developer.apple.com/forums/thread/727877 praying for a quick solution, it breaks the quality assurance for our apps...

Thanks a lot for pointing that to us. I did not have the reflex to have a look to the release notes. The reason is probably that there is absolutely no warning at all in Xcode : the function is still here, it can be activated, and no information is provided. It's confusing, but in same time, I'm not surprised at all. Since Xcode server has been half-working for a few years, without any updates, this conclusion was already obvious. What is even more confusing is how it's possible that Apple's Xcode team (which, I imagine, is composed of more than one person) gives so little care in communicating about a feature that can have a pretty huge importance in terms of quality assurance for developers projects. I accept being a ***** that saw macOS server disintegrating, Xcode cloud emerging, and still believed that he could use Xcode server until the last minute, instead of following the wind direction. Still, it's a bummer, on so many levels.

ok, so, @John, we have an answer : https://developer.apple.com/forums/thread/727877?page=1#750139022

Hi john. Have you been able to move forward on this ? I'm still interested in knowing how I could make Xcode Cloud faster....

Have you ever been able to figure out a solution ? We are spinning in circles here to try and understand what could go wrong, but we still don't have a clue after several hours of brainstorming....

We just managed to fix our problem without being sure of why and how :) basically : we had a trigger for "tag change" which did not seem to work. While editing the workflow, the expected tag was not printed in the search list. And, again, the job was not triggering as expected. we added a manual trigger to the workflow. Started a manual build. and then pushed again a tag change on the remote repository, which has triggered, as expected, the automatic start of the workflow. So, nothing fancy here, just a little bit of old school "shut up and do as I say". l.