{"version":"2.1.319","anchor":"gateway-sign-in-expiry-stops-telemetry-and-settings-polls","canonical_anchor":"gateway-sign-in-expiry-stops-telemetry-and-settings-polls","heading":"An expired Cloud gateway sign-in now pauses telemetry and settings checks","tier":"notice","area":"LLM Gateway","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/gateway-sign-in-expiry-stops-telemetry-and-settings-polls","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### An expired Cloud gateway sign-in now pauses telemetry and settings checks\n\nWith an expired Cloud gateway sign-in, telemetry is not sent and you are told to run `\/login`, and background settings checks are skipped\n\n**What**\n\nWhen your Cloud gateway sign-in has expired, two background jobs stop:\n\n- Telemetry: each batch of usage data that would be sent fails with a message saying it was not sent and asking you to run `\/login` to reconnect.\n\n- Remote settings: the regular background check for settings managed from elsewhere is skipped.\n\n**Why**\n\nIf you use a Cloud gateway, these messages tell you that your sign-in has lapsed and that `\/login` fixes it.\n\n- Area: LLM Gateway\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}