Skip to main content
Use this page to choose the next concrete action when Cogno setup, import, integration, machine, or docs behavior does not match what you expected. Each guide page carries its own quick Symptom · Cause · Fix table for the common case; this hub goes deeper, walking each symptom through Check and Next actions steps. For machine health specifically, see Manage your machines.

​
Start here

​
Desktop requires an update

Cogno may require the current signed desktop release before the rest of the app opens. This screen cannot be dismissed. Select Update Cogno to begin. While Cogno downloads and installs the release, the screen shows a progress bar and three update highlights in your interface language. Swipe horizontally or use the three page indicators to move between them. Cogno restarts automatically after installation. When the updated app opens, select Continue on the welcome screen. If an in-app update is unavailable, Update Cogno downloads the signed installer instead; install it and reopen Cogno. If the update reports an error, select Try again or Download installer. If an optional update fails from the floating update control, select Try again or Open download page to get the newest signed release manually.

​
Sign-in and workspace access

​
Cannot sign in

Check:
  1. You are using the same sign-in method you used to create the account.
  2. For a new email account, enter the latest six-digit confirmation code from your inbox on the sign-up screen. You may read the email on another device, but enter the code in the browser that started sign-up.
  3. For Google or Apple sign-in, confirm the browser can complete the auth callback.
  4. If you came from an invite link, open the invite link again after signing in.
  5. If the auth callback shows an error page, capture the visible error text.

​
No workspace appears

Check:
  1. Open the workspace selector.
  2. Confirm you are signed in with the expected account.
  3. Ask a workspace owner to send a new invite link from Settings → Members.
  4. If you have permission to create one, use Create workspace.
Check:
  1. Sign in first.
  2. Open the invite link in the same browser.
  3. Ask for a fresh invite link from Settings → Members.
  4. Confirm the workspace owner can still see you in the member list after accepting.

​
Workspace settings

​
Settings shows invalid workspace

The URL may contain a workspace ID that is not available to your account. Next actions:
  1. Go back to the Cogno app root.
  2. Select a workspace from the workspace selector.
  3. Ask the workspace owner to confirm membership.

​
General settings fails to load

Next actions:
  1. Refresh the page.
  2. Confirm you can open the same workspace from the main Tasks page.
  3. Confirm your account still appears in Settings → Members.
  4. Capture the visible error text.

​
Workspace delete is disabled

Check:
  1. The workspace has a non-empty title.
  2. You typed the exact workspace title in the confirmation dialog.
  3. You understand deletion removes tasks, chat history, members, and workspace data, and cancels any current Business subscription immediately.

​
Task CSV import

​
CSV file is rejected

Cogno requires a header row and at least one task row. Next actions:
  1. Open the CSV in a spreadsheet or text editor.
  2. Confirm row 1 contains headers.
  3. Confirm at least one later row contains task data.
  4. Export again as CSV.

​
Mapping complete is disabled

Every CSV column must be mapped or explicitly ignored. Check:

​
Imported rows are skipped

Rows can be skipped when validation fails. Common causes: Next actions:
  1. Map a stable parent ID, title, source URL, or external key to Parent Task.
  2. Keep each parent row in the same import when possible.
  3. Keep source IDs or URLs as Source or Metadata.
  4. Re-import children after parents exist when migrating in separate files.

​
Imported tasks miss context

Next actions:
  1. Preserve source URL as Source.
  2. Map labels, priorities, milestones, numbers, issue keys, and custom fields to Metadata.
  3. Use multiple Description columns when long context is split across columns.
  4. Keep comments or detailed text in metadata when no direct Cogno field exists.
See Import task CSVs into Cogno.

​
Integrations

​
Integration card is not clickable

The integration may be marked Coming soon. Available integrations open a detail page; unavailable cards are dimmed and carry a Coming soon badge.

​
Google Calendar does not connect

Next actions:
  1. Open Integrations → Google Calendar.
  2. Select Connect my Google Calendar.
  3. Complete the Google account flow.
  4. Return to the integration page and confirm your member row shows connected.
Each member connects their own Google Calendar.

​
Calendar meetings do not get a notetaker

Check:
  1. The member invited to the meeting connected their own Google Calendar.
  2. The event has a meeting link (Google Meet, Zoom, Microsoft Teams, or Webex).
  3. Have Cogno join is on for the event under Upcoming meetings. Recording settings lock within 10 minutes of the start, so set them earlier.
  4. The event is present on the connected calendar. Shared and delegated calendar events are also eligible.
  5. The integration page shows the account as connected.
If a connected teammate is invited to the same meeting, one notetaker covers it for the workspace.

​
API keys and machines

​
Raw API key is no longer visible

Create a new key. Cogno shows the raw key once after creation and never shows it again.

​
API key creation fails

Check:
  1. You are a member of the workspace.
  2. You have fewer than 25 active keys for this user and workspace.
  3. The key name is 255 characters or less.

​
Machines shows only a list of machines in the browser

Settings → Machines manages the computer you are on, so most of it needs the Cogno desktop app. In a browser only the Your machines roster renders — every computer signed in to your account, each shown as online or offline. Open the same page from the desktop app to see This machine (the Engine status for this computer), Startup & background, Registered Environments, and server enrollment.

​
A project has no folder to run in

An environment is a folder on your machine plus the settings work runs under there. Each member connects their own folder from the project’s settings — Settings → Machines does not keep a list of folders. Next actions:
  1. Open the project’s settings (the gear on the project) and find the Environments section.
  2. If your row reads No folder connected, select Choose folder to pick a folder on this computer, or Clone repositories to clone the project’s repositories into a new location.
  3. Do this from the Cogno desktop app on the computer that holds the folder. In a browser, select Open in the Cogno app.
See Set up a Project for the whole page.

​
A machine cannot pick up work

Check:
  1. Engine is running on that computer. Settings → Machines → This machine shows its state — Running, Stopped, or Not running — with Start, Stop, and Restart controls. On macOS the close button only puts the window away; Quit Cogno in the menu bar is what ends it.
  2. The machine has network access. This machine shows Last check-in and whether the server sees it checking in.
  3. The Readiness line is Ready. When it is not, the details list what blocks it — for example the agent CLI not installed or signed out, git or Node.js missing, the GitHub CLI signed out, or the disk almost full.
  4. If the credential was rejected or revoked, use Reset & re-register or sign the machine in again from the same panel.
  5. For a server you enrolled, run cogno doctor on it. Each check reports a verdict, and a failing check prints the command that fixes it. See Run Cogno on your own server.

​
Revoking a key cut a machine off

For a machine you run from the CLI, create a replacement key and re-authenticate on that machine:
For an enrolled server, run cogno server install again — revoking cuts every credential generation at once, so the server has to be admitted again.

​
Memory

​
Memory fails to save

Next actions:
  1. Refresh Settings → Memory.
  2. Confirm you are still signed in.
  3. Make a small edit and save again.
  4. Copy the visible error text if saving still fails.

​
Memory content renders incorrectly

Memory is Markdown. Check headings, bullet indentation, fenced code blocks, and unclosed links.

​
Docs

​
Copy for LLM does not copy

Check the browser’s clipboard permission, make sure the page has focus, and confirm privacy settings are not blocking clipboard writes.

​
Wrong language appears

Use the language switcher in the top navigation, or open the page directly for the language you want:

​
Escalation package

When you need help from a teammate or assistant, collect:
  1. Workspace name or ID.
  2. Page URL.
  3. Exact visible error text.
  4. Action that produced the problem.
  5. Whether the issue reproduces after refresh.
  6. Sanitized screenshot or terminal output.
  7. Related file header or sample row for CSV import issues.
Remove API keys, private tokens, customer data, and personal contact details before sharing.