Troubleshooting
What each refusal actually means, and which gesture it asks for — including the failures that are correct behaviour rather than bugs.
Shipped in the current build. You can do this on your own machine today.
Most of what looks like a failure here is a refusal, and a refusal names its gesture. The table separates the two, because trying to fix a deliberate refusal wastes an afternoon.
#A provider will not connect
| What you see | What it means | What to do |
|---|---|---|
| not installed | No binary of that name is on the path. | Install the vendor CLI, then let Finexia look again. |
| signed out | The binary answers, the session does not. It looks like it works, and it is the most common case. | Sign in — from Finexia for two of the three vendors, from the CLI itself for the third. |
| timed out | The sign-in ran past three minutes. | Retry. Nothing is broken; a browser sign-in simply took longer than the deadline. |
| failed, with a reason | The attempt failed and Finexia says why in its own words. | Read the reason: it names the gesture. The CLI’s own message is deliberately not shown, because it carries an email address and a token path. |
| no sign-in button at all | That CLI has no sign-in command to drive. | Set the environment variable it reads, or sign in once from the CLI’s own interface. |
#A card produces nothing
- Read the trace first. Every line is an event from a real process; if the trace is empty, the process never started, which is a provider problem and not a mandate problem.
- Open the raw output underneath the trace. It carries the exact command line, and the card is meant to be reproducible by hand from it.
- If a tool call came back flagged as an error, that is the tool refusing with a reason — not the server breaking. The reason is written for the agent to act on, and it is worth reading yourself.
#A request is refused before anything runs
- PLANNEDA slide deck or a PDF was asked forNeither format has an engine. Preflight refuses before a process starts, which is why the refusal is instant and costs nothing. Ask for a workbook instead.
- AVAILABLEA tool is not in a card’s listThe role does not hold the capability that tool requires. It is not hidden as a locked door — it does not exist for that role. The reference page shows which roles hold which tools.
- AVAILABLEA connector was refused at declarationThe role you assigned it to reads your own data, and a connector reaches outward. The two never combine. Assign it to a role that does not read the desk or your deposits.
- AVAILABLEA tool answered that a key is missingSome data vendors need one. The tool refuses cleanly and says so rather than silently switching to another source — which would give you a number whose origin you could not name.
#A process outlived the application
Quitting from the application stops every process it started. A hard kill from outside bypasses that path by definition, and one orphan was observed exactly that way. That is the expected behaviour of a signal, not a leak — but if you kill the application from outside, check for a leftover CLI process yourself.
#The answer says BLOCKED
That is a result, not a failure — often the most honest one available. It means the question could not be answered at the as-of date with admissible sources, and the mandate said so instead of approximating. The blocked artefact carries what was attempted and why it stopped; the contract refuses to deposit it otherwise.
#Sources
- Finexia OS — product state at 0.0.23FinexiaInternal document, not published
- The provider registry, mirrored on this siteFinexiaInternal document, not published
- The tool registry, mirrored on this siteFinexiaInternal document, not published