const CREDENTIAL_RETRY_COOLDOWN: Duration;Expand description
How long to skip re-attempting this agent’s credential pipeline (provisioning OR token fetch) after either step fails, before trying again. InjectAvailable broadcasts for ANY injection to ANY agent, so without this an agent whose pipeline can’t currently succeed (quota exceeded, malformed agent_id, provisioning/token endpoint down) gets a fresh network round-trip on every single broadcast — an unthrottled retry storm, unlike the broker’s single-flight-guarded scheduler used for the shared token. reagentx P2 on PR #2342 (round 1: provisioning only; round 2: also covers fetch_m2m_token, the gap round 1 left open for an already-provisioned agent whose token endpoint is failing).