Webflow Interactions: Choosing Between Implicit Revert and Custom Cleanup on Timeout Cancellation

Determine the appropriate cleanup strategy when a Webflow Interaction timeout is cancelled due to page navigation or a new trigger before the timeout elapses.

The platform allows setting an "On timeout" action (revert, continue, or stop) but does not expose a dedicated callback for timeout‑cancellation events. When a cancellation occurs, Webflow clears the pending timeout and applies the default revert behavior, which may vary across browsers or change in future releases, leaving developers uncertain whether to rely on this implicit revert or to implement custom cleanup via code embeds.

What are the risks of relying on the implicit revert behavior for timeout‑cancellation across different browsers and future Webflow updates? How can developers detect a timeout‑cancellation event without a documented callback? Is implementing custom cleanup through custom code embeds justified given the possible impact on interaction performance?