Limits of ngrok automatic rollback after a failed upgrade

Goal

Assess whether ngrok’s automatic rollback feature, triggered by version pinning in the configuration file, can consistently restore the client to the specified previous release after an upgrade failure.

Constraints and uncertainty

The rollback behavior may vary between ngrok client editions and the cloud service tier, and significant version gaps can introduce configuration incompatibilities. Additionally, residual cloud‑side tunnel state might persist after a local rollback, and the automatic rollback guarantee is not documented for all plan levels.

• Does ngrok’s automatic rollback revert the client binary to the exact pinned version when the upgrade command reports a failure, regardless of the ngrok plan?
• If the rollback succeeds, are there any known scenarios where cloud‑side tunnel endpoints retain settings from the failed version, requiring manual cleanup?