Quick answer: Drive the radial Image fill amount from remaining time over duration, and set the fill origin and clockwise flag to match the visual you want.
An ability cooldown overlay fills in instead of wiping away, or sweeps counterclockwise. The fill value or origin is inverted. Here is how to fix it.
How to fix it
1. Feed remaining time, not elapsed
Set image.fillAmount = remaining / duration so the overlay shrinks as the cooldown completes; use elapsed only if you intend it to grow.
2. Set fill origin and direction
On the Image set Filled type, choose Radial360, and set the fill origin (Top) and fillClockwise to match the sweep you want.
3. Clamp and hide at zero
Clamp fillAmount to 0..1 and disable the overlay when the cooldown ends so a tiny residual fill does not linger over the icon.
Catching the ones you can't reproduce
The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.
Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.
This is where a tool like Bugnet earns its place. Its SDK captures every Unity error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.
Reproduce it once with full context and the fix writes itself. The hunt is the expensive part.