Troubleshooting

In the messages below, "Backend team" and "Acme" stand for your team's and your organization's names.

Signing in

Message	What to do
"Sign in to see your teams."	Press Sign in, or run HQ: Sign In.
"No org has developer access on yet. An org owner turns it on in HQ, under Settings, Security."	An organization owner turns on Developer access in HQ, under Settings, Security. Then run HQ: Refresh.
"The sign-in was denied in the browser."	Someone chose Deny on the approval page. Sign in again.
"This sign-in code expired. Sign in again."	The 10 minutes ran out. Start over.
"HQ for VS Code is not available on this HQ yet."	This HQ address does not offer the extension. Check the hq.host setting.
"Signing in to AI Workforce One HQ from another VS Code window. Finish there; this window picks it up."	Finish the sign-in in the other window.
"Your HQ sign-in needs renewing."	Press Sign in.
"Your access to HQ from this computer ended. Sign in again."	This computer was removed in HQ, or your access ended. Sign in again.
"... is not an HQ address this editor may use. ..."	Set hq.host back to https://hq.aiworkforceone.com.
"The HQ address changed. Sign in again to use it."	hq.host changed. Sign in again.
"Your HQ sign-in is stored without the system keychain on this computer."	Not an error. On Linux, start a keyring (for example GNOME Keyring or KWallet) and sign in again if you prefer the keychain.
"This version of AI Workforce One HQ is no longer supported. Update it from the Extensions view."	Update the extension.
"HQ could not be reached. Check your connection and try again."	Check your network, then try again.

Teams and sessions

Message	What to do
A team shows off	Its machine is not running. Press Wake Team, or open one of its sessions and press a key.
A team shows update needed	Its machine needs an update for the extension. An owner or admin presses Update machine in HQ, under the team's Settings.
A team or session shows view only	You have viewer access to the team, or the session is someone else's. You can watch but not type or save.
"Could not load sessions"	Run HQ: Refresh. If it repeats, open the team in HQ.
"Backend team did not start within 3 minutes. Check it in HQ and try again."	Open the team in HQ to see its state, then try again.
"Backend team has no machine yet. Open the team in HQ and start a session to start it."	Start a session on the team in HQ once.
"Too many wake requests for this team. Wait a few minutes and try again."	Wait a few minutes.
"This team is at its session limit. Stop a session in HQ, then try again."	Stop a session you no longer need.
"Your plan is read-only. Reactivate billing in HQ to save files or start sessions."	An owner updates billing in HQ. Reading still works.
"You can view this team but not start sessions on it."	You need editor or owner access to start a session.

Terminals

Message	What to do
"Backend team is off." / "Press any key to wake it."	Press a key to wake the machine.
"Connection lost, reconnecting..."	Progress: the terminal reconnects on its own.
"The connection to HQ was lost. Close this terminal and attach again."	Close the terminal and open the session again.
"You can watch this session but not type in it."	Your access changed while the terminal was open. You can still watch.
"Your access to this session ended."	Your access changed, or the session was closed.
"You cannot open this session from this computer."	Your access to the team or to Developer access changed. Run HQ: Refresh.
"Instant local echo is off for Acme. ..."	An owner or admin turns on Instant local echo in HQ, under Settings, Security. The terminal works without it.
"Local echo is not available on this HQ yet."	The terminal works without local echo.
"HQ local echo is off in this terminal because VS Code's own local echo is on (terminal.integrated.localEchoEnabled)."	Set terminal.integrated.localEchoEnabled to off to use HQ's.

Files

Message	What to do
"Backend team is off. Wake it to open this file."	Press Wake Team, then open the file again. Files you already opened stay readable.
"Backend team is off. Wake it to save this file."	Press Wake Team, then save again.
"This file changed on the team machine. Save again to compare."	Save again, then compare or overwrite.
"You can view this team but not change its files."	You have viewer access to the team.
"This file came from an AI Workforce One HQ template, so it is read-only."	Template files on a template team cannot be changed.
"This file contains masked secret values. Edit it from an HQ terminal."	Change it from a session terminal, or the secret in HQ.
"This file is too large to open here. Open it in HQ or from a terminal."	Use HQ or a session terminal for that file.
"This file's name has control characters HQ can't open. Rename it on the machine."	Rename the file from a session terminal.
"This team is not available on this sign-in. Sign in, or refresh the Teams view."	Run HQ: Refresh, or sign in again.
"Backend team's machine is updating. Its files are back in about 2 minutes."	Wait for the update to finish.
"Live file updates for Acme are paused: ..."	Too many editor windows are open for this sign-in. Close other HQ windows. Files still refresh every minute.
"The search did not run: ..."	Read the reason, then search again.

Ports

Message	What to do
"Port 9229 cannot be forwarded: the team machine uses it itself."	Forward another port. HQ refuses the Docker API, the Node debugger and the machine's own ports.
"Backend team started before Developer access was turned on. Restart it once (Restart machine in HQ team settings) and ports will forward."	Developer access was turned on while the machine was running. An organization owner or admin presses Restart machine in the Machine section of the team's Settings in HQ. Sessions pause for about two minutes and come back where they were.
"You cannot forward ports from Backend team."	You need editor or owner access and an active plan.
"Backend team is off. Wake it, then forward the port again."	Press Wake Team, then forward again.
"Backend team is stopped. Start it from the team page in HQ, then forward the port again."	Start the team in HQ.
"Could not forward the port: the port is already in use on this computer"	Something on this computer already uses that port. Forward again and pick another port on this computer.
"The forward of port 3000 ended."	HQ ended the forward. Click it in the Ports view to start it again.

Still stuck?

Email support@aiworkforceone.com with the extension's version (in the Extensions view), your editor's name and version, and the exact message.