Troubleshooting

This page addresses common issues and questions that arise when using Pilot.

Seed data and live data

Pilot supports local seed data and real ontology data:

• Editor view uses seed data generated inside the Pilot container by default. Where supported, the editor also offers a Production data preview. A separate production-data viewer can analyze real data where enabled, with a review step before sharing its analysis. See Work with data.
• Deploy view connects your application to real ontology data. On a deployment branch, ontology schema changes (object types, action types, link types) are scoped to the branch and do not affect Main until you merge. On Main, any actions you perform in the application are live ontology edits that take immediate effect.

Permission errors during deployment

Deployment requires permissions at the project, organization, and enrollment levels. If you encounter permission errors, verify the following:

• You have at least the Editor role on the Foundry project where Pilot is deploying.
• You have permission to create the Developer Console application in its folder and create its linked OAuth client in the organization, typically granted through the Third-party application administrator role.
• A user with domain-approval permissions has approved the subdomain request in Control Panel > Approvals.
• The project does not have marking restrictions that block dataset creation.

For a full breakdown of Developer Console permissions, see Developer Console permissions. If permissions appear correct but errors persist, check the browser console for detailed error messages and share them with your administrator.

Access Pilot logs

To access Pilot system logs:

1. Select the three-dot menu (...) next to the tab bar in the content header.
2. Select Pilot diagnostics.
3. Inspect Pilot logs.

The diagnostics view displays the latest 500 log lines. Select Copy logs to copy them or follow the link to Code for full logs. Use these logs to diagnose build errors, dependency installation issues, and runtime problems.

Build errors in the Preview tab

If the Preview tab shows a build error instead of your application:

1. Read the error message in the Preview tab. Common errors include missing imports, type mismatches, and syntax errors.
2. Select Fix with Pilot to prompt Pilot to diagnose and resolve the issue automatically.
3. If the automatic fix does not resolve the issue, describe the error in the chat panel and ask Pilot to investigate.

You can also check Pilot logs in diagnostics for detailed build output from the development server.

Container startup issues

After you create a new application, Pilot provisions a container. Startup time depends on provisioning and dependency installation. Check the following if the container does not start:

1. Check the status monitoring popover by selecting the status indicator in the top-right corner. The Pilot status field indicates whether the connection is healthy.
2. If the status shows Disconnected, try refreshing the page.
3. Inspect dependency and development-server errors in diagnostics. If the failure persists, provide the error and relevant logs to Palantir Support.

Unintended edits in deploy view

When previewing your application in deploy view on Main, any actions you perform, such as creating, editing, or deleting objects, are live ontology edits that take immediate effect on production data. This is expected behavior, not a bug.

This also applies in editor view when Production data is selected.

If you want to test actions without affecting production, preview your application in deploy view on a deployment branch instead. Object edits made by actions on a branch are not merged into Main. Ontology definitions are merged separately. External side effects have separate rules; see Branching action types.

Action references break across environments

When you deploy ontology entities from a Pilot branch to Main, action type identifiers (RIDs) may differ between the branch and Main. This can cause reference errors if your application code references branch-specific RIDs.

To resolve this issue:

1. After merging your branch, switch back to Main in Pilot when prompted.
2. If errors persist, ask Pilot to update action references to use the Main branch identifiers.

Divider element console errors

You may see error messages in the browser console referencing "divider" elements with no height. Check whether the affected component is visible and usable. If a widget is invisible in Workshop, check its row-height setting as described below.

Dependency installation failures

Try the following steps if the status monitoring popover shows that npm dependencies failed to install:

1. Select Fix with Pilot in the status popover to attempt automatic resolution.
2. If the issue persists, check Pilot logs in diagnostics for specific error messages.
3. Ask Pilot to reinstall dependencies by typing Reinstall npm dependencies in the chat panel.

Application does not deploy

Follow the steps below if the deployment panel shows that your application is not deployable:

1. Open the status monitoring popover and check Deployability for deployment dry-run errors or a failure to load the local Ontology definition. Use its Fix with Pilot action to address the reported error.
2. Check the Ontology tab separately for type-checking and edit-permission errors. These can remain even when Deployability shows Deployable. Ask Pilot to correct the reported issue.
3. Inspect dependency, development-server, and release CI errors separately. The Deployability status does not report these checks.
4. After fixing issues, retry the deployment from the deployment panel.

On a protected code branch, implement fixes on an editable branch and merge them through a proposal. See Branches, changes, and proposals.

Custom widget preview does not load

If the Preview tab shows a blocked or empty frame, inspect the browser error before changing configuration. Unable to load widget preview can also indicate a timeout. If the browser reports a Content Security Policy violation, ask the appropriate administrator to review the required container origin. Also check build errors, dependencies, and the selected widget. See Develop and preview a widget set.

Custom widget is invisible in Workshop

Check the widget's Display > Row height setting. A generated widget that uses the full height of its container can have zero visible height with Auto (max). Use Flex or an appropriate Absolute height for a widget designed to fill its container, or ask Pilot to make the widget size itself from its content. See Auto sizing.

Save the Workshop layout and verify that the controls are visible and usable in View.

Custom widget changes not reflected in the preview

Changes to a widget's parameters or events are not applied to the running preview until the widget development server reloads. Select Reload widget dev mode in the widget preview to apply configuration changes.

If Reset clears the preview configuration fields but the rendered widget retains its previous values, select Reload widget dev mode and verify the result again.

A control is missing or disabled

Inspect the explanation shown for a disabled control or the reported error. Common causes include:

• Pilot is still working or another repository operation is in progress.
• The current code branch is protected or deleted.
• The repository does not support the capability.
• The feature is unavailable in the current enrollment or Pilot version.
• No suitable model is available.

For branch restrictions, see Branches, changes, and proposals. For model availability, see Models and agent modes.

Production-data analysis is unavailable

Production-data analysis requires a supported environment and feature configuration. Production preview alone does not imply that the analysis feature is available.

If an analysis cannot be found in the review dialog, ask Pilot to create a new one. If reading an object type fails, inspect the reported permissions or data error before retrying. See Production-data analysis.