I am seeing this behaviour where Tag Event source stops getting events on start. I am trialling out the git based server config. When I restore the configuration in a new instance I see that the tag events are not coming in.
To provide an update on this behavior, along with the title change, this has been identified as a bug with tag paths using wildcards failing to subscribe on start-up. The workaround is to restart the event stream in some manner, either by changing the stream or disabling and re-enabling the stream, which should allow for the source to subscribe to the paths correctly. Using explicit paths, as Robert noted, would allow you to avoid this issue in the meantime.
This bug is relevant for the wildcards ** and any number of ?, but it does not apply to the single * which subscribes as expected on start-up.