{"version":"2.1.259","anchor":"client-wait-minutes-now-clamped-to-a-numeric-range","canonical_anchor":"cloud-review-poll-timeout-now-server-configurable","heading":"Cloud\/bughunter poll timeout driven by remote config client_wait_minutes","tier":"notice","area":"Code Review","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.259\/e\/client-wait-minutes-now-clamped-to-a-numeric-range","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.259","markdown":"### Cloud\/bughunter poll timeout driven by remote config `client_wait_minutes`\n\nThe remote wait-minutes value is now clamped between 30 and 55, defaulting to 45 when unset or invalid.\n\nThe remote-config value `client_wait_minutes` is now read and clamped to a finite number between 30 and 55, falling back to 45 if it is unset, non-numeric, or out of range. This replaces the previously hardcoded 30-minute (`1800000`ms) timeout used by the remote\/cloud-review task poller before it declares `poll_timeout`; the value is computed once (memoized) and reused everywhere the timeout is checked or reported, including the timeout error message. The same value is used to compute `BUGHUNTER_RESULT_RELAY_MAX_SEC` for the bughunter feature's result-relay wait time.\n\n- Area: Code Review\n- Names: `client_wait_minutes`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}