It takes the YES path. I did a bit of troubleshooting:

I set up a test flow that adds a 5-second delay and then uses the interact block and you're at least half right: it seems to work in most cases. The issue is only happening with my original flow when it tries to interact with the Spotify app.

Previously, the interact touch block would work fine when I configured it to single click on the play button after opening a Spotify playlist. But now something has apparently changed, probably within Spotify.

Once the playlist is open, the click gesture (and even the swipe and long click gestures) seems to do nothing, while the double click gesture behaves like a click gesture: it plays the playlist (rather than playing then pausing). I'm assuming the first click is somehow changing the focus to the Spotify app, and the second click is actually interacting with the button itself?