compliance-errors changedmanage-claude/compliance-errors
Nearest release: v2.1.317, published 2 hours before this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Recorded here
Lines+16added
Lines−0removed
From line
132
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits16to this page, all time
### Invalid file ID
The whole hunk
from line 132, old and new numbered
/
from line 132
132132
133133For the first body, resend the unmodified `next_page` value from the previous response to the endpoint and session that issued it. For an expired cursor, restart without a `page` parameter; the new walk reflects the retention boundary in effect when it starts, so messages that aged out of the retention period in the meantime are no longer returned (see [Retrieve a local session transcript](https://platform.claude.com/docs/en/manage-claude/compliance-sessions#retrieve-a-local-session-transcript)).
134134
135### Invalid file ID
136
137**Type:** `invalid_request_error`
138
139```text wrap
140Invalid claude_gen_file_id format: 'claude_file_01Qm7RzKdTgWnYbVx3HcLpE5'
141```
142
143```text wrap
144Invalid claude_file_id format: 'claude_gen_file_01TbR8wAcCeFhJkLnPqStUvX'
145```
146
147**Cause:** The ID in the path is not in the form the endpoint accepts. The generated-file endpoints (`/v1/compliance/apps/chats/generated-files/*`) accept only `claude_gen_file_...` IDs and return the first body for any other value. The file endpoints (`/v1/compliance/apps/chats/files/*`) accept only `claude_file_...` IDs and return the second body. The `generated_files` array on a chat message can hold both kinds of ID.
148
149**Fix:** Choose the endpoint by the ID’s prefix, not by the array the ID came from; see [Retrieve files and artifacts](https://platform.claude.com/docs/en/manage-claude/compliance-content-data#retrieve-files-and-artifacts). If the prefix already matches the endpoint, the ID was truncated or altered; copy it again from the response that returned it.
150
135151### Transcript page too large
136152
137153**Type:** `invalid_request_error`
No line in this hunk matches that.