DOC-API-MODEL-schema-1ftcunpmha#overview
FileResolutionConfig
Configuration for resolving CONTENT_PART_TYPE_FILE_ID parts to fresh signed URLs before requests are sent to LLM providers. Keeps stable file references in message history while generating ephemeral URLs only when needed.
Omitting the file-resolution failure mode uses FILE_RESOLUTION_FAILURE_MODE_SKIP_CONTENT, which silently drops an unresolvable part. A resolved URL can also expire before a later attempt; a fresh URL on every attempt is not guaranteed. With FILE_RESOLUTION_FAILURE_MODE_FAIL_GENERATION, an unresolvable required part fails the run before the provider call. This can happen after asynchronous send acceptance; inspect the correlated run outcome rather than expecting the initial HTTP response to report the later failure. Verify that the report was actually available before presenting its summary.
Type-reference view: API Schema 9frhv4euve, API Schema 9ftjkkjhfa. Request and response views describe this type; they do not declare an endpoint.
Meaning and usage
Section ID: DOC-API-MODEL-schema-1ftcunpmha#meaning
See the definition above.
Usage profiles
Section ID: DOC-API-MODEL-schema-1ftcunpmha#fields
| Usage | Fields and validation |
|---|---|
| In requests | View fields |
| In responses | View fields |
In requests
Section ID: DOC-API-MODEL-schema-1ftcunpmha#request
API JSON uses JSON field names (camelCase).
| Field | Type | Presence | Meaning |
|---|---|---|---|
Section ID: DOC-API-MODEL-schema-1ftcunpmha#request-field-failuremodefailureMode | string (FILE_RESOLUTION_FAILURE_MODE_FAIL_GENERATION, FILE_RESOLUTION_FAILURE_MODE_SKIP_CONTENT) or integer (int32) | Optional; explicit presence | Action to take when a file cannot be resolved. If omitted, skip unresolved file content and use the remaining content. |
Values of failureMode
Section ID: DOC-API-MODEL-schema-1ftcunpmha#request-values-failuremode
How generation handles a content part whose file identifier cannot be resolved.
| Value | No. | Form | Meaning |
|---|---|---|---|
FILE_RESOLUTION_FAILURE_MODE_FAIL_GENERATION | 0 | Canonical | See meaning below. |
FILE_RESOLUTION_FAILURE_MODE_SKIP_CONTENT | 1 | Canonical | See meaning below. |
FILE_RESOLUTION_FAILURE_MODE_FAIL_GENERATION
Fail generation when a file content part cannot be resolved.
Fail the entire generation if any file resolution fails.
FILE_RESOLUTION_FAILURE_MODE_SKIP_CONTENT
Skip the unresolved content part and continue with the remaining content.
Skip failed content parts and proceed with available content (graceful degradation).
In responses
Section ID: DOC-API-MODEL-schema-1ftcunpmha#response
API JSON uses JSON field names (camelCase).
| Field | Type | Presence | Meaning |
|---|---|---|---|
Section ID: DOC-API-MODEL-schema-1ftcunpmha#field-failuremodeSection ID: DOC-API-MODEL-schema-1ftcunpmha#response-field-failuremodefailureMode | string (FILE_RESOLUTION_FAILURE_MODE_FAIL_GENERATION, FILE_RESOLUTION_FAILURE_MODE_SKIP_CONTENT) or integer (int32) | Optional; explicit presence | Action to take when a file cannot be resolved. If omitted, skip unresolved file content and use the remaining content. |
Values of failureMode
Section ID: DOC-API-MODEL-schema-1ftcunpmha#response-values-failuremode
How generation handles a content part whose file identifier cannot be resolved.
| Value | No. | Form | Meaning |
|---|---|---|---|
FILE_RESOLUTION_FAILURE_MODE_FAIL_GENERATION | 0 | Canonical | See meaning below. |
FILE_RESOLUTION_FAILURE_MODE_SKIP_CONTENT | 1 | Canonical | See meaning below. |
FILE_RESOLUTION_FAILURE_MODE_FAIL_GENERATION
Fail generation when a file content part cannot be resolved.
Fail the entire generation if any file resolution fails.
FILE_RESOLUTION_FAILURE_MODE_SKIP_CONTENT
Skip the unresolved content part and continue with the remaining content.
Skip failed content parts and proceed with available content (graceful degradation).
Where used
Section ID: DOC-API-MODEL-schema-1ftcunpmha#where-used
| Reference | Relationship |
|---|---|
| Create an agent profile | POST /api/v1/agent-profiles/create |
| Get an agent profile | POST /api/v1/agent-profiles/get |
| Import a prompt library | POST /api/v1/agent-profiles/import |
| List agent profiles | POST /api/v1/agent-profiles/list |
| Update an agent profile | POST /api/v1/agent-profiles/update |
| Withdraw your rating on a message | POST /api/v1/llm/delete-message-rating |
| Get full conversation state | POST /api/v1/llm/conversation-state |
| Rate an assistant message | POST /api/v1/llm/rate-message |
| Send a message and wait for the result | POST /api/v1/llm/send-message-sync |
| Submit client-side tool results and wait for the next segment | POST /api/v1/llm/submit-client-tool-results-sync |
| Update context management settings | POST /api/v1/llm/update-context-management-settings |
| Update default generation config | POST /api/v1/llm/update-default-generation-config |
| Get the caller's end-user profile | POST /api/v1/enduser/get |
| Append a message without generating | POST /api/v1/llm/append-message |
| Create a new conversation thread | POST /api/v1/llm/create-thread |
| Send a message to a conversation | POST /api/v1/llm/send-message |
| Update the caller's default generation config | POST /api/v1/enduser/update-generation-config |
| ReceiveMessageRequest | API JSON uses JSON field names (camelCase). |
| ClientToolDispatch | API JSON uses JSON field names (camelCase). |
Models containing this value
| Model | Relationship |
|---|---|
| GenerationConfig | Nested in model |
| GenerationConfig | Nested in model |
Download the public reference contract.
Document ID: DOC-API-MODEL-schema-1ftcunpmha