'realtime algorithm has been deactivated'

If that’s the reason, then Cubase should point us right to these conflicting markers. For ten minutes now I’ve been searching a quite long audio event with mikroskopic precision, but couldn’t find any markers that appear to be too close. Also, how close is “too close”? I need Audio Warp back to work again! (And get rid of this annoying message)

BTW, I’m dealing with markers made from hitpoints. Why would Cubase set these error provoking markers in the first place?

To @dave007
Hi! Please mark @Benjamin_Blue’s reply as the solution (if what he suggested also worked for you)
This reply I mean: