{"version":"2.1.304","anchor":"policy-pending-errors-for-file-attachments-and-richer-polic","canonical_anchor":"policy-pending-errors-for-file-attachments-and-richer-polic","heading":"Organization policy loading records more failure detail, and file attachments wait for it","tier":"notice","area":"File Attachments","scope":"org","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/policy-pending-errors-for-file-attachments-and-richer-polic","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Organization policy loading records more failure detail, and file attachments wait for it\n\nOrg policy fetches now record server error codes and auth denials, and attaching files before the policy loads returns a policy_pending error\n\n**What**\n\nIn organizations that manage Claude Code centrally, Claude Code fetches the organization's policy limits and remote settings from a server. This release changes what happens when that fetch fails or has not finished yet.\n\n- Attaching files now fails with the error code `policy_pending` while the organization policy has not loaded. The message tells the model to try again in a minute and, if it is refused again, to tell the user. A `digest_mismatch` size and digest check used to sit at this point.\n\n- The policy-state reason now carries `policy_server_error_code` and `policy_server_auth_denial`, and the result includes `httpStatus`.\n\n- Loading policy limits can now run as a single attempt (`singleAttempt`, which runs as `accelerated_retry`). It skips the retry that has no verdict when the trigger is `api_refusal_trigger`.\n\n- The startup load now records the server error code, whether access was denied, and the last attempt (`startupLoadServerErrorCode`, `AuthDenial`, `LastAttempt`). Before, only the server error type was recorded.\n\n- Remote settings fetches also record the server error code and auth denial when they fail or get no response.\n\n- Refreshing the cached policy now passes along how old the cache is.\n\nThe related setting `tengu_rustling_orbit` was read as off for this site's account and for the anonymous baseline, and no reading has been taken under this release yet.\n\n**Why**\n\nIf you attach a file before your organization's policy has arrived, you get a clear retry message instead of a generic failure. The extra error detail mostly helps admins and support work out why a managed policy fetch failed.\n\n- Area: File Attachments\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: yes"}