Troubleshooting

FixControl tries to make every refusal say what failed, why, and what to do next. This page collects the ones people hit most, with the text you will see and what is really going on.

Ask Command Center first. It answers for your specific case: "Is this project ready?", "why did this check fail?", "why can't this change be applied?", "why is this release blocked?", "what is waiting on me?", "which workspaces can I enter?" and "where does our work come in?". It can also act: "get this project ready" starts clearing what it can clear.

No mail arrives in the Inbox

What you see	What it means	What to do
A forwarding mailbox shows Set up, waiting for the first email	Forwarding is not set up or not confirmed yet.	Finish the forwarding at your mail service and send a test message. See Connecting e-mail.
Sign-in no longer works	The consent at Microsoft or Google was revoked or expired.	Reconnect under Settings → Mailboxes.
Mail arrives, but no issue is created	Automatic issue creation is off for the mailbox (the default), or the mailbox has no project.	Use Create issue, or have an administrator switch on automatic creation and link a project. See Inbox.
A reply cannot be sent	Allow replies is off for the mailbox (the default).	Have an administrator switch it on under Settings → Mailboxes.

The chat bot does not react

The bot only reacts to /fix, a mention, a direct message, or a reply in a thread it already works in. If it asks you to link your account, run /fix link. If a decision from chat is refused, your chat account is not elevated or your role in this workspace may not decide. See Communication channels.

Tickets created directly in Freshdesk, Linear, Odoo or TOPdesk do not become issues by themselves. FixControl creates tickets from issues and follows their status. A Jira ticket does become an issue when Import new Jira tickets as issues is on for the project's Jira link and the Jira webhook is set up; if it does not arrive, check both, and that the ticket matches the link's Jira project or component.

A project says it is not ready

Readiness is composed, so the answer is usually one missing piece. The usual suspects, in the order they bite:

No repository connected — open the project's Connections and choose Connect repository.
No verified environment — FixControl has not yet proved how to build and start the application. Open Environments and start a verification.
A question is waiting — under What FixControl needs to know, answer it and choose Answer and retry.
Verified, but without a start command — normal: the tests ran, nothing was launched. The card says so and offers to find a start command.
A connection is set up but not tested — use its test under Connections.

A test will not go green

Start with why it is not green — the three causes are genuinely different.

The tests failed. That is about your code, and it is the one case that leads to a new, AI-prepared revision. Where it is switched on, the developer agent first investigates inside the container the run failed in; you see that on the run as What the agent found in the failed container.

The environment failed. An image that would not load, a dependency that would not install, a service that never became ready. This never turns into a proposed change to your code.

The application did not start. Tests green, start broken. You see Did not start under Did the application start?, and the patch will not be delivered. If the start command itself is wrong, fix it under Environments → Environment settings and choose Save and verify.

Two results that are not a verdict: Tests never ran — no verdict (an earlier step stopped the run) and Tests ran nothing — no verdict (the test step selected nothing). See Verification and results.

"This check never ran"

The run stopped before it ran, and the message names what is missing. The common case today:

A .NET Framework or WinDev project. FixControl detects it and plans the real build and test commands, but it does not run them today: the Windows environment for .NET Framework is built but not switched on or proven, and WinDev needs a licensed PC SOFT installation that FixControl does not provide. The message names exactly what would be needed. This is a refusal, not a silent pass.
This run had no project. The issue is not linked to a project, so there was no test environment. Link the issue to a project and run the verification again.

A patch will not apply

In order of frequency:

An approval is still open. Check Approvals — the card names who it is waiting for.
The test did not pass, or belongs to an older version. Evidence is fingerprinted over the patch, the images, the configuration and the plan. Change any of them and the old green run no longer covers the new state; run the verification again.
The application-start proof is missing. The environment knows how the application starts, but no run showed that it does. The card says: The tests passed but nothing proved the application still starts; rerun the verification so its start target is exercised. For a project validated only in your own environment, see Change validation.
A required test environment has not run. With Docker first, then your environment, both have to pass. A local pass never stands in for the other.

See Delivering changes.

An approval is waiting and nobody can give it

By default one active admin or manager decides. If staged approvals are switched on, each stage is decided by whoever holds that role, one person per stage, so a route with three stages needs three different people. If nobody holds a role, the stage falls back to any admin or manager. If your organization has no active admin or manager at all, the gate keeps waiting. See Approvals.

A preview will not open

Previews are on by default, but a workspace can switch them off, and they need a verified environment with a start command underneath.

previews are switched off for this workspace — an admin or manager can switch them on under Settings → Overview & progress.
Did not start with a reason line — the application did not come up. The phase line shows how far it got.
This project must be validated on your own runner — a project that requires validation in your own environment gets no preview.
The page loads but has no styling. The application uses absolute asset paths and your FixControl deployment has no per-preview hostnames yet. That is set up by FixControl, not from the project.

A preview always ends by itself, and stopping it loses nothing — the evidence lives on the run.

I cannot switch to a workspace

What you see	What it means	What to do
Being deleted	Deletion has been scheduled; the data is still there during the restore window.	FixControl platform staff can restore it within the window.
Blocked	The workspace is suspended.	Ask your FixControl contact.
Not listed at all	You have no membership there.	FixControl platform staff grant access to a second workspace.
"Could not switch workspace" with a two-factor message	The target workspace requires two-factor authentication.	Set up or confirm two-factor, then switch again.
"Could not switch workspace" and signing in again fixes it	Your session was revoked, usually because your role changed.	Sign in again.

Switching changes the workspace for every open tab. See Switching workspaces.

A connection shows a problem

Health is shown per capability, never as one blanket "connected". A mailbox that can receive but not send shows exactly that. When something fails, look at the connection's status under Settings → Channels, the delivery status on the issue or approval that needed it, and the audit log. An external write is queued, retried and, if it keeps failing, reported.

Something happened that I did not expect

Governed decisions are recorded: who decided, when, on what evidence, through which channel. Admins and managers can browse them under Settings → Audit (visible with Show advanced settings). On the Pro and Enterprise plans the log can be exported as a signed CSV that proves the file was not changed after export. Decided approvals cannot be edited afterwards, and deleting a project, issue or integration does not delete the record of what was decided about it.

Still stuck

Tell your FixControl contact three things: the workspace, the exact text on screen, and the id of the run, patch or issue. Refusals are written to be quotable on purpose.