Troubleshooting
Each entry gives what you see, the cause the app itself reports, and what to do. Messages quoted here are the app's own words.
Sign-in
| You see | Cause | Do |
|---|---|---|
| The button says Finish signing in in your browser… and nothing happens | The browser tab did not open or you closed it before finishing | Wait for the listener to time out (5 minutes), or quit and reopen the app, then choose Sign in with Orkestia again. Pop-up or default-browser settings can stop the tab opening |
sign-in timed out | The browser never returned to localhost within 5 minutes | Sign in again and finish in the browser straight away |
port 5174 is in use (…) | Both loopback ports the sign-in may use (5190, then 5174) are taken by other programs | Close the program holding the port, or restart the computer, then retry |
| Sign-in state mismatch — please try again. | The state in the browser's answer differs from the one this attempt created. A common cause is a sign-in tab left over from an earlier attempt | Close old sign-in tabs and start again from the app. Do not reuse a browser tab from before |
| The sign-in page returned no code. | The hosted page ended without a code | Start again. If it repeats, sign in on app.orkestia.dev first to check the account itself works |
| The hosted page's own error text (for example from a blocked or unconfirmed account) | The page returned error and error_description; the app shows the description | Fix the account on the web, then retry |
| The browser says the site cannot be reached after you signed in | A local firewall or security tool blocks localhost:5190 | Allow loopback connections for the browser, then retry |
127.0.0.1 only, answers only the one callback path, and answers anything else with a 404. It shows Signed in. You can close this tab and return to Orkestia Cockpit. in the browser when the callback arrives.Signed in on the web but the app asks again
The app and the web keep separate sessions that share an account. Signing in on one does not sign you in on the other; the hosted page may skip the password if your browser session is still valid.
Session expired
Your session expired. Sign in again. means the platform refused to renew your session: the refresh was rejected (a 4xx answer other than 429). It happens after a long absence, a password change or an account change on the platform.
A network error or an unreachable platform does not sign you out; the app keeps your session and retries. If you see Couldn't refresh in the toolbar instead, see The window says Couldn't refresh.
Sign in again. Your sidebar arrangement, selections and drafts stay (they are not tied to the session).
Notifications do not show
- Choose Send Test Notification (account menu, ⌘K, or Help on macOS).
- Test notification sent. and nothing appeared: the system is blocking the app. On macOS allow Orkestia Cockpit in System Settings › Notifications. On Windows and Linux check the system notification settings and focus modes.
- Notifications are blocked: …: the system refused outright. Allow the app, then try again.
- Notifications only work in the desktop app.: you opened the interface in a browser.
- Check who the decision is for. Only decisions addressed to you notify. A decision for someone else shows in Decisions but never raises an alert.
- Check how many arrived at once. Up to three new decisions each notify. More than three become one N new decisions summary.
- The app announces each decision once. The list of announced decisions is part of the cache; if you cleared the cache, pending decisions can notify again.
- Closing the window keeps watching from the tray. Quit Orkestia Cockpit stops it. Open the tray menu and check the app is still running.
- The Dock or taskbar badge counts decisions waiting on you plus chat mentions and direct messages. If the number looks wrong, press ⌘R (Ctrl+R) to refresh.
On macOS notifications go through the system's notification center, so a notification for an app that was reinstalled or renamed can need the permission granted again.
Updater errors
| You see | Meaning | Do |
|---|---|---|
| Couldn't check for updates with Retry | The background check failed (offline, the update store unreachable) | Retry, or Later to hide it until a check succeeds |
| Could not check for updates: … dialog | The same, from a check you started. The reason follows | Retry later. If the reason names a signature, the download was not signed by the update key: do not install it, and report it |
| Update didn't finish | Download or install failed. The message is the updater's own | Close it, retry from About, or install the latest installer from a fresh link |
| No Updates Available | You are on the latest version for your platform | None |
| No update shown on a Mac that the other platforms have | The Mac build of that version is published separately and was not published yet | Wait for it, or ask for a new installer |
| Every installed copy stops finding updates at once | The read link to the update store expired or was removed | Install again from a new link. After that the app updates itself |
If a version you dismissed with Later is the one you want, open Settings › About › Check for Updates…: a check you start always shows the sheet.
Organization mismatch
The organization name at the top of the sidebar can show a ⚠ with the tooltip Workflows run in
The window says Couldn't refresh
The toolbar shows Live when updates arrive as they happen. Couldn't refresh (hover for the reason) means the last read failed; the app keeps the previous data on screen and keeps trying, on a poll of about 15 seconds when the live connection is not up. Press ⌘R (Ctrl+R) to force a read. If it persists, check your connection and your organization role for the view.
The window disappeared
Closing the window hides it and keeps the app in the tray. Click the tray icon or choose Open Cockpit. On macOS click the Dock icon. Starting the app a second time also brings the existing window forward.
Where the app keeps its data
| What | Where |
|---|---|
| Sign-in tokens | The OS secure store, service dev.orkestia.cockpit (macOS Keychain, Windows Credential Manager, Linux Secret Service) |
| Settings, sidebar, drafts, recent searches | The webview's local storage for the app |
| Window size and position | The app's window state file |
| Everything else | The platform. Nothing about your organization is only on this computer |
To start clean without losing access: Settings › About › Cache › Clear…. To remove the sign-in too: Sign Out. To remove everything the app wrote: sign out, quit, then remove the app and its folder named dev.orkestia.cockpit under the per-user application data location of your operating system. Treat the exact path as depends on the platform.
See About, settings and updates for what Clear… removes.
About, settings and updates
What Settings contains in the Cockpit app, the About panel (version, update, resource usage, cache, account), appearance, and exactly what clearing the cache removes
CRM
Orkestia's built-in CRM keeps the people who reach your app as contacts, tracks each one as a lead through your stages, and records every touch on one timeline, through twelve crm workflows you can call directly
