VS Code

Troubleshooting

Common Astra login, org connection, workspace, MCP, and metadata workflow issues that are directly supported by the current extension behavior.

Login issues

Browser did not open

If login cannot open your browser, run Kognyt: Log In again and make sure your editor can open external links.

Login timed out

The login flow times out after 5 minutes. Start the login flow again and complete the browser step before the timeout.

Org connection issues

No active org

If a tool reports no connected org, select one with Kognyt: Select Org.

Connect org asks you to log in first

Kognyt: Connect Salesforce Org requires a Kognyt session. Sign in first, then retry.

Org connection timed out

If org connection polling times out, run Kognyt: Sync Org Metadata and then re-check the org list.

Workspace issues

No workspace folder open

Retrieve and deploy require an open workspace folder.

Retrieve cannot find package.xml

Create manifest/package.xml or provide package_xml_path in the retrieve tool input.

Deploy target could not be inferred

Open a metadata file first, or provide explicit deploy paths.

Local Salesforce CLI backend issues

If astra.metadataExecutionBackend is localSfCli:

  • set astra.sfCliTargetOrg
  • make sure the CLI target resolves to the same org ID and instance URL as the active Astra org

The local CLI backend also does not support every flag. Current limits include:

  • no single_package retrieve
  • no single_package, allow_missing_files, or auto_update_package deploy
  • run_tests only with RunSpecifiedTests

MCP and provider setup

If a supported provider was not configured automatically, run Kognyt: Setup AI Provider.