{"version":"2.1.280","anchor":"retrybackoff-delay-schedule-introduced-as-explicit-constant","canonical_anchor":"retrybackoff-delay-schedule-introduced-as-explicit-constant","heading":"Retry\/backoff delay schedule introduced as explicit constant","tier":"internal","area":"Internals","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/retrybackoff-delay-schedule-introduced-as-explicit-constant","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Retry\/backoff delay schedule introduced as explicit constant\n\nA new explicit delay schedule (500ms to 60s) was added, likely for retries or reconnection\n\n**Unclear.** The finding does not say which request or reconnection flow uses this schedule.\n\n**What**\n\nA new constant defines a schedule of delays in milliseconds: 500, 1500, 4000, 15000, and 60000. This looks like a backoff schedule used to space out repeated attempts, such as retrying a request or reconnecting.\n\n**Why**\n\nHaving this as a named, standalone schedule suggests some retry or reconnection flow now waits progressively longer between attempts rather than retrying at a fixed or unspecified interval.\n\n- Area: Internals\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}