The error you are seeing is a GraphQL schema mismatch: the client (both the browser app and the VS Code extension) is querying a field `latestVersionV3` on the `ThirdPartyApplication` type that the backend GraphQL schema does not recognise. Because this reproduces in both the browser and locally, it is almost certainly a platform-side regression rather than a stale local extension — a frontend deployment was likely updated to reference a field that was removed or renamed on the backend (or vice versa).
This is not documented as a known issue in the available documentation, so the most important immediate step is to **file a support ticket** with Palantir, including your Trace ID `5926a92dd4cc466d`. That ID will let the platform team pinpoint the exact failing request and the deployment mismatch.
-–
## Interim workaround: edit `resources.json` directly
While the resource panel UI is broken, you can still add resources by manually editing the `resources.json` file that the TypeScript v1 template maintains in your repository. This file has full Git semantics, so changes are reviewable and revertable.
The expected format is:
```json
{
“version”: 1,
“objectTypes”: [
{ "rid": "ri.ontology.main.object-type.<locator>" }
],
“linkTypes”: [
{ "rid": "ri.ontology.main.link-type.<locator>" }
],
“sources”: [],
“functions”: [],
“valueTypes”: [],
“functionInterfaces”: [],
“_comment”: “”
}
```
To find the RIDs of the object or link types you want to add, navigate to **Ontology Manager**, locate the type, and copy its RID from the resource details panel. Once you save the file and commit, Code Assist will restart and regenerate the code bindings automatically.
-–
## For the VS Code local extension specifically
The Palantir VS Code extension is not available on the VS Code Marketplace and must be re-downloaded directly from the platform each time a new version is released. If your locally installed extension version is behind the current platform version, it can compound schema mismatch issues. To rule this out:
1. Navigate to a Code Repository in the browser.
2. Select the settings icon next to the **VS Code** button and choose **Local VS Code**.
3. Re-download and reinstall the `.vsix` file.
However, given that the browser-side panel is also broken, re-downloading the extension alone will not resolve the root cause — that requires the platform-side fix.
-–
## Summary
| Action | Purpose |
|—|—|
| File support ticket with Trace ID `5926a92dd4cc466d` | Root cause fix — platform schema mismatch |
| Edit `resources.json` directly with RIDs from Ontology Manager | Unblock resource additions while UI is broken |
| Re-download VS Code extension from the platform | Rule out stale local extension as a compounding factor |