Palantir Foundry Error Triage

Overview

Triage the failing surface before changing credentials, permissions, code, or compute. Preserve the server request identifier and Foundry build evidence so similar-looking failures are not collapsed into the same cause.

Prerequisites

• Capture the exact status code or Foundry error name, request identifier, timestamp, endpoint or build, and affected principal.
• Identify whether the call uses a temporary user token, authorization-code token, or client-credentials service user.
• Read references/official-docs.md; use the API reference and in-platform build report as the current contract.
• Reproduce with a read-only request or sandbox branch whenever possible.

Current Contract

• A 401 points to missing, malformed, expired, or otherwise unusable authentication; it does not justify broader scope.
• A 403 can result from the intersection of token scope, application restrictions, user/service-user permissions, project roles, and mandatory controls.
• Foundry documents global rate and concurrency limits, while individual endpoints may impose stricter limits and return 429 or 503.
• Transform preview and full build can differ because preview may use a subset of data; repository checks also evaluate dependencies and declared resources.