{"version":"2.1.232","anchor":"remote-control-stops-retrying-forever-when-the-server-is-unr","canonical_anchor":"remote-control-stops-retrying-forever-when-the-server-is-unr","heading":"Remote Control stops retrying forever when the server is unreachable","tier":"notice","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/remote-control-stops-retrying-forever-when-the-server-is-unr","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Remote Control stops retrying forever when the server is unreachable\n\nRemote Control now gives up after roughly 30 minutes of failed reconnects and tells you why.\n\n**What**\n\nWhen a Remote Control session drops because presence heartbeats are failing (close code 4093), the credential re-mint loop now gives up after about 14 attempts and fails the session with a plain explanation that it could not reach the server for about 30 minutes, instead of retrying indefinitely.\n\n**Details**\n\n- The cap applies only to close code 4093. Other close codes still retry without a limit.\n- Successful reconnects and the existing recovery-exhausted path now report how many re-mint attempts were made.\n\n**Evidence**\n\n`could not reach the Remote Control server for about 30 minutes`\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}