Code Workspace fails to start with PERMISSION_DENIED

Ask the Community
,
1

I’m working through the “Your First Ontology Function” training, but I’m unable to start the Code Workspace for my Functions repository.

The repository was created successfully, but every time I open the workspace it enters a failed state with the following error:

Error code: FAILED_TO_START_SESSION
Related error: RemoteException: PERMISSION_DENIED

The page says that an unexpected error occurred while starting the session. Restarting the workspace produces the same result.

I have already confirmed:

  • I am an organization administrator.
  • Code Workspaces access is enabled for everyone.
  • The repository was created successfully.
  • Restarting the workspace does not resolve the issue.

Because the workspace never starts, I cannot access the VS Code-style editor or continue the Functions portion of the course.

Has anyone encountered this before? Is there another permission that must be enabled for Functions or dedicated developer workspaces, or does this require Palantir support to correct on the backend?

Workspace/repository: My First Function BBaysinger

Enrollment: Dedicated Developer

Browser: Chrome on macOS

2

Summary

The FAILED_TO_START_SESSION / PERMISSION_DENIED error is likely a backend compute session provisioning issue, not a repository access or user permission problem. The error occurs when the platform attempts to create the compute environment required for a VS Code session and is denied before any resources are allocated.

Key Findings

  • Repository access appears to be functioning correctly since the repository can be created and accessed.
  • The failure occurs during compute session startup, indicating an infrastructure or authorization issue rather than a UI-level permission problem.
  • Immediate and repeatable failures typically point to a configuration or authorization restriction rather than a transient system error.
  • Feature enablement (e.g., Code Workspaces being turned on) and compute provisioning authorization are separate controls and may not be configured consistently.

Recommended Checks

  • Verify that workspace and compute access are not restricted to specific user groups or roles.
  • Confirm the repository is being opened through the supported VS Code workflow from within the code repository interface.
  • Review any enrollment- or environment-specific restrictions that may limit compute session provisioning.

Likely Root Cause

The most probable cause is a compute authorization restriction associated with the environment or enrollment configuration. The platform is allowing repository access but blocking the creation of the underlying compute container required for the VS Code session.

Recommended Resolution

Escalate the issue to platform support and provide:

  • Environment or enrollment name.
  • Repository identifier.
  • The exact error message: FAILED_TO_START_SESSION / PERMISSION_DENIED.
  • Confirmation that workspace functionality is enabled in the organization settings.
  • Details of the troubleshooting steps already performed.

If the Issue Persists

Because the failure occurs before the workspace is provisioned, further user-level configuration changes are unlikely to resolve the problem. Platform support will need to verify and correct the backend authorization or compute provisioning configuration.