Sections
Questions and troubleshooting
Answers to common questions about the agent and what to do about each error message.
Common questions
I don't have an "Agent" button. The agent is in preview and is being enabled for accounts gradually. If there's no button in the project header or in the menu, it hasn't been enabled for your account yet. If you open the agent URL directly, you'll see "This section is unavailable."
Can the agent see my code? No. The built-in agent has no access to the repository, file system or command line. It only knows what's recorded in the Flownix project: nodes, comments, documents, components, Artifactory files.
Will the agent change something without asking? No. The agent changes the tracker only when you ask. Deletion, archiving, applying spec deltas and changing the project policy each require a separate "Allow". The agent doesn't follow requests written inside tasks and files — those are data, not commands.
How do I see exactly what the agent did? Every action is a tool card in the feed with its arguments and result; at the end of the reply there's a "What was done" block. In the project action log the changes are signed "Flownix Agent".
How do I undo what the agent did? There's no "undo turn" button. Ask the agent: "revert the statuses of the tasks you changed in your last reply" — it sees in the history what it did. Or fix things by hand using the links in "What was done".
Can my colleagues see my sessions? Yes. Agent sessions are shared among project members. Only the author can delete a session. See Team work.
Can I attach a file to a message? No. Upload the file to Artifactory and mention its slug. The agent reads text files up to 1 MB on its own; images, PDFs and archives it can't.
The agent forgot what we discussed at the start.
Long conversations get compacted: at 70% of the context window the early part is replaced with
a summary. It's better to record important things in the project — ask the agent to leave a
[decision] comment on the task. For a new topic, start a new session.
The agent answered incorrectly. Click "Regenerate reply" or "Edit message" and refine the request. If the mistake repeats, use "Leave feedback" in the "The agent is in development." banner at the top of the chat — it's the best way to make the agent better.
How do I view an archived session? You can't yet: the interface has no archive view. Archive only what you don't plan to come back to.
Why does the agent refuse to answer? The agent is a specialist in Flownix and your project. It politely declines off-topic questions.
Error messages
| Message | What it means | What to do |
|---|---|---|
| Credits are used up. Resets {date}. | The monthly credit limit is used up | Wait for the reset on the 1st or switch to a higher plan |
| Monthly agent credit limit reached. | The same, a server response when sending | The same |
| Credits are running low: N of M | Less than 20% of the limit is left | Economize: new sessions, precise requests |
| The agent is not available on your plan. | Your plan has no agent credits | Change the plan |
| This model is unavailable on your current plan… | The selected model isn't included in your plan | Choose another model or change the plan |
| The plan’s concurrent turn limit has been reached… | The maximum number of replies is already running across your sessions | Wait for one of them to finish |
| Too many concurrent agent turns… | The same, a global limit | Wait for the current ones to finish |
| Too many requests to the agent. Retry in N s. | More than 10 new turns per minute | Wait the stated time |
| The agent is still replying. Wait for the turn to end. / A turn is already running in this session. | A reply is already running in this session — yours or a colleague's | Wait or stop the reply |
| Turn aborted: step limit reached. / …took too long. / …length limit reached. | The turn hit a limit | Click "Continue" |
| Turn stopped. | The reply was stopped with the "Stop" button | What was done before stopping is kept; continue with a new message |
| Model failure. Please try again. | A temporary model error | "Retry" |
| The turn failed. / Internal agent error. | A failure on the Flownix side | "Retry"; if it repeats, "Leave feedback" |
| No connection: the message was not sent. | The connection to the server was lost | Check your network; the indicator in the header will show "Connected" |
| Please sign in again. | Your sign-in session expired | Sign in to Flownix again |
| Session not found. | The author deleted the session | Start a new one |
| The agent has been temporarily disabled by an administrator. | The agent is turned off for maintenance | Try again later |
| text is too long | The message is longer than 16 KB | Shorten it or upload the text as a file to Artifactory |
| too many sessions in this project (limit 500)… | You have 500 sessions in the project | Delete old sessions |
Connection indicator
The agent header shows the connection state: "Connecting…", "Connected", "Reconnecting…", "Disconnected". If the connection drops, the agent keeps working on the server: after reconnecting, the feed catches up with what happened, and during the outage the status line shows "Connection lost — reconnecting…".