==========
When scrying a target that is unable to be located for any reason, such as being warded, or them going through a transition, it triggers the 10 minute cooldown. I can't find my source, but this was confirmed to not be intended behavior, and until today, hasn't been a bug.
Steps to reproduce
----------------------------
Scry someone that produces the failure message, 'cannot be located.'
Expected result
-----------------------
Cooldown doesn't trigger, and scry can be immediately used for another target.
Actual result
-------------------
Cooldown triggers, and character is unable to scry as if they'd successfully scried someone.
Screenshot(s)
--------------------

Misc Notes
----------------
Which Server(s)?
------------------------
Guldorand
Gaming Platform(s)?
------------------------------
PC - Steam