Messages

On the Boards page

Message	Cause	Fix
No board’s automations will run until a working OpenAI key is added. Automation runs on your company’s own OpenAI key, and none has been added yet.	No key.	Add one on the OpenAI Key page. The boards stay editable meanwhile.
No board’s automations will run until a working OpenAI key is added. Your company’s OpenAI key is failing: reason.	The key was rejected, ran out of credit, reached a hard limit, or cannot use a model.	Fix it in your OpenAI account, then Re-verify, or enter a new key.
Whether ticket automation can run could not be checked: the OpenAI key status could not be read.	A temporary failure.	Open the OpenAI Key page, or reload.
Editing is unavailable … These settings are shown live, so they cannot be changed while they cannot be read.	The settings could not be read live. Every control is disabled.	Retry.
This board is switched off. Nothing runs on it, not even Preview, and no AI is used on its tickets, in MTX or AI clients, until you switch it on. You can set it up first.	The board is off.	Switch on, when you are ready.
Checking whether the API member may add attachments…	Split Tickets was just ticked.	Wait a moment.
Split Tickets cannot be switched on yet … the API member’s security role role may not add attachments.	Your ConnectWise API member lacks Manage Attachments at Add level.	In ConnectWise, System → Security Roles → role → Companies → Manage Attachments, Add Level All; then Check again.
Split Tickets cannot be switched on yet NilearX could not read the API member’s security role: reason	The role could not be read, for example because ConnectWise rejected the keys.	Fix the cause named, then Check again.
Splits whose screenshots belong to a moved issue are left for a technician until the API member may add attachments.	A board already splitting, whose API member lacks the right.	As above.
Support Advisor is switched off for your company. Switch it on	Shown on the Support Advisor checkbox.	See Support Advisor.
Not available for PSA yet	Your PSA is not ConnectWise. Ticket Automation reads boards from ConnectWise only.	None for now.
No boards to configure	Your ConnectWise returned no service boards.	Check your service boards in ConnectWise; then Re-read boards from your PSA.
The number of tickets on this board could not be read from your PSA, so there is no monthly total.	The cost estimate’s ticket count failed.	Nothing; each automation’s cost per ticket is still shown.
The OpenAI cost estimate could not be loaded. It is read again when you re-read the boards.	A temporary failure.	Re-read boards from your PSA.
Couldn’t save your last change	A switch, tick or choice was not saved.	Make the change again.
Still saving — you may be offline. Do not close this page.	A save is taking long.	Check your connection.

On the Global Instructions page

Message	Cause	Fix
AI instructions unavailable … Instructions are shown live, so they cannot be changed while they cannot be read.	The instructions could not be read live.	Retry.
A list of findings with Save anyway and Keep editing	The check found something the automation cannot follow.	See Write instructions.
Saved without being checked: they are too long to check / the check is unavailable right now / the check took too long to answer.	The check could not be made. The text was saved.	Check later, if you like.
No problems found. The AI can follow these instructions.	Check found nothing.	None.

On the OpenAI Key page

Message	Cause	Fix
Ticket automation and Support Advisor are paused. Add your company’s OpenAI key below to start them.	No key.	Add one.
Ticket automation and Support Advisor are paused. Your key is failing: reason.	The key is failing.	Fix it in your OpenAI account and Re-verify, or enter a new key. Nilear re-checks a failing key every hour.
Allow these models in the key’s OpenAI project: models.	The key’s project is limited to selected models.	In the OpenAI project’s model settings, allow all models, then Verify and save again.
Usage could not be read.	A temporary failure.	Retry.

For the notes Ticket Automation writes on tickets, see Note headings and lines.