Build is not sometimes trigged by tag

Hi!

We are using a tagging system and the feature "Use tags as branches" to trigger a tag to a certain environment / configuration.

It works properly most of the times. But sometimes it doesn't register.

We have a "Build" environment / configuration which detects all commits and build at a certain interval.

Then we have a "Development" environment / configuration which detects tags from the same VCS.

So if we tag Release/Development/[commit hash]

It will build and create a release (using octopus deploy) to our Development environment.

What I think happens is that somehow the "Build" trigger, or "Build" current running a build interfere with the trigger of "Development".

Is there any scenario you can see this happens? I can see pending changes on "Development" configuration and I can see the proper tag in git.

But there is no "branch" created for the tag and thus do not trigger a build and release creation for "Development".

If I delete the tag and apply it again it works. So I want to figure out why at some cases it does not detect it.

"Development" is using the same VCS root as "Build". Maybe the checkout stops it?