Troubleshooting
Troubleshooting
This page lists the error messages and notices of AnyLLM verbatim — in the chat, in suggestion cards, in the history, in the settings, in the Confluence quick actions and in the dashboard gadget — with their cause and the solution. If you are looking for a message, use your browser's search on this page.
Check these first
- Can you see the chat at all? If not, or if it only shows a notice → The app does not start or is locked.
- Is the input field locked (placeholder Configuration by an admin required.)? Then the app is not set up yet → same section. (An inactive subscription does not lock the field; it only blocks sending — see below.)
- Does the error occur in Jira and in Confluence? Both products share one configuration, so a problem in only one product almost always means that the AI endpoint is not yet approved for that product (message "The endpoint … is not approved for … yet — endpoint approvals apply per product. …") or that Confluence is not connected to the app.
- Did it happen only once? Network-related interruptions occur. Send once more before reporting it.
The app does not start or is locked
| Message | Cause | Solution |
|---|---|---|
| Not set up yet with "The chat is available once an admin has configured the app."; input field shows Configuration by an admin required. | no saved configuration, or no connection with a stored API key | administration: Setting Up LLM Connections |
| "Not configured yet — an administrator sets the endpoint, models and API key in the app settings (Jira: Settings → Apps · Confluence: Settings → AnyLLM)." (chat banner) | same as above | same as above |
| "Not configured yet — an admin must set up connections and API keys in the app settings." (quick actions, chat bar answers, dashboard gadget) | same as above | same as above |
| "The AnyLLM subscription for this site is inactive — an administrator can review it in Atlassian administration (Billing)." (chat) · "… — an administrator can review it in Atlassian administration." (quick actions) · "… — an admin can review it in Atlassian administration." (server, e.g. in the gadget) | the paid subscription is inactive. Only new answers and ✓ Execute are blocked; history, memory, own agents and skills and all settings keep working | administration: check the subscription in Atlassian administration — see Licence, Data Retention and Automatic Deletion |
| "This feature has been disabled by your administrator." (in the page assistant, the issue action and the issue navigator with a Close link; in the gadget in view and edit mode; on the standalone full page) | this particular surface is switched off under Modules; menu entries cannot be hidden per installation | use a different entry point, e.g. Apps → AnyLLM Chat; administration: Modules |
| ⤢ Fullscreen on a Jira issue opens only the disabled notice | the module Fullscreen chat (Jira) is switched off | administration: Modules |
| "Page access for the AI is disabled by your admin — page actions are unavailable." (page quick actions greyed out) | AI access is set to Off | actions on selected text keep working; administration: General Settings |
| "Configuration could not be loaded." | the settings were briefly unavailable | reload the page; if it recurs, inform the administration |
| The chat bar in Confluence has disappeared | Dismiss was clicked (applies to the current view only), the surface is switched off, the app is not set up, the subscription is inactive, or the status could not be loaded — the bar shows no message in any of these cases | reload the page. The bar's status is cached in your browser for ten minutes, so after the administration has switched it back on or completed the setup it can take up to ten minutes before the bar reappears |
| The Settings button is missing in the chat | you are not an administrator — in Confluence the button appears only for members of the usual administrator groups | open the settings via the product: Jira Settings → Apps → AnyLLM Chat — Settings, Confluence Settings → AnyLLM Chat — Settings — see Opening the Settings and Initial Setup |
Messages while chatting
The request does not get through
| Message | Cause | Solution |
|---|---|---|
| "No response from stream (timeout) — please try again." | nothing arrived from the stream for 60 seconds | send again; if it recurs, inform the administration |
| "Stream error." / "Call failed (invocation error or timeout)." | processing was interrupted | send again |
| "Hourly limit reached (… requests/hour) — please try again later." | your personal hourly limit is reached. One counter covers Jira and Confluence together; every send counts (including ↻ Regenerate answer, quick actions and gadget refreshes); the window starts with your first request and ends one hour later | wait. The administration can adjust the limit — General Settings |
| "Please enter a prompt." | an empty message was sent | enter some text |
| "Connection not configured or has been removed." | the connection behind the chosen model was removed or has no API key any more | choose another model in the Model selector or reload; otherwise administration |
| "The endpoint … is not approved for … yet — endpoint approvals apply per product. An administrator can grant it in the AnyLLM settings of … under “Endpoint approvals”." (shown in your interface language) | the AI address is not approved in this product — typical right after importing a configuration, or when it was only approved in the other product | administration: Managing Endpoint Approvals |
The AI service refuses
| Message | Cause | Solution |
|---|---|---|
| "LLM endpoint rejects the API key (401/403)." | API key wrong, expired or without permission | administration: renew the key — Setting Up LLM Connections |
| "Rate limit of the LLM endpoint reached (429)." | quota at the AI provider exhausted | wait a moment; if it persists, administration |
| "LLM endpoint responded with HTTP …" (followed by the service's reply) | the service reports an error | administration checks address, model names and quota |
| "Timeout after 120s — shorten the prompt or choose another model." | one round of the model took longer than 120 seconds | ask a shorter question or choose another model |
| "LLM call failed: …", possibly with "This endpoint needs a network approval: check that an administrator has approved it under Settings → Endpoint approvals." | the service could not be reached; with the addition, the address is not approved | administration: Managing Endpoint Approvals |
| "The LLM response was empty or had an unexpected format." | the service answered in a form the app does not understand | administration checks the provider type and the model names |
| "Internal stream error." | an unexpected error while streaming | send again; if it recurs, inform the administration |
The answer stays empty or breaks off
| Message | Cause | Solution |
|---|---|---|
| "The model used its token budget (8000) on internal reasoning without answering — shorten the prompt or choose a non-reasoning model." | the model spent the whole response budget on internal reasoning | ask a shorter question or choose a model without an internal reasoning phase |
| "Model is thinking …" for a long time | the model is reasoning internally before text is produced | wait; if this happens permanently, the administration may choose a different default model |
| "I proposed an action — please confirm or dismiss it above." | the AI only produced a suggestion card and no text | click ✓ Execute or Dismiss on the card |
| The answer was there and is gone after Stop | Stop only hides the display; the request continues on the server | open the conversation again from History — the complete answer may be there |
| The AI no longer remembers earlier parts of a long chat | only the most recent 16 messages (about 32,000 characters) are sent to the AI, although the history keeps everything | repeat the important facts, or start a new chat with a short summary |
| The AI stops after a few lookups or does not finish a multi-step task | per answer the AI may look things up in at most 5 rounds (each up to 120 seconds, the whole answer at most 5 minutes); lookup results are cut at 8,000 characters | split the task into smaller questions |
Display
| Message | Cause | Solution |
|---|---|---|
| Images appear as the link "view external image" | deliberate: images are not loaded automatically, so that no image can report data to the outside world unasked | click the link to open the image in a new tab |
| "Diagram could not be rendered:" | the model delivered faulty diagram code; the code is shown below | ask the AI to correct the diagram |
| "Mermaid could not be loaded:" | the diagram library could not be loaded | reload the page |
| Tool steps show English labels such as "Jira search: …", "Reading issue …", "Web search: …" | these status rows are always English | — |
Messages for actions in Jira and Confluence
Most of these messages appear on a suggestion card after ✓ Execute; a few, marked as such, come from the AI's own lookups and reach you only in its answer. Success messages are partly German even in the English interface: "✅ Vorgang ABC-1 erstellt.", "✅ Vorgang ABC-1 aktualisiert.", "✅ Comment added to ABC-1.", "✅ Page "…" created in space …" — each followed by a link.
| Message | Cause | Solution |
|---|---|---|
| "Write actions are not enabled by the admin." | AI access is not Read + write — also when the administration changed it while the card was open | ask the administration to enable Read + write — General Settings |
| "This feature has been disabled by your administrator." | the surface was switched off meanwhile | use another entry point |
| "Required field missing: …" | a required field is missing in the proposal | ask the AI to repeat the proposal with that field |
| "Field too long: …" | a field exceeds 32,000 characters | have a shorter text generated |
| "Invalid field: …" / "Invalid arguments." / "Unknown action." | the proposal is malformed | ask the AI to propose again |
| "Nothing to update: provide a new summary and/or description." | an Update Jira issue card without a new summary or description | ask the AI for concrete changes |
| "No access to Jira-Suche (user permissions insufficient)." / "No access to Vorgang ABC-1 (user permissions insufficient)." / "No access to Seite erstellen (user permissions insufficient)." | you lack the rights in Jira or Confluence | clarify the rights in the project or space |
| "Vorgang ABC-1 was not found." (on a card; for lookups the AI may also report "Seite 123 was not found.") | the issue or page does not exist or is invisible to you | check the key; the AI can list the projects and spaces visible to you |
| "Space "DOCS" was not found." | the space key is wrong | state the correct key |
| "Seite erstellen: Atlassian API responded with HTTP 400." | Confluence rejected the page — most often a page with this title already exists in the space | choose a different title |
| "Vorgang erstellen: Atlassian API responded with HTTP …" / "Kommentar auf ABC-1: Atlassian API responded with HTTP …" / "Vorgang ABC-1: Atlassian API responded with HTTP …" | Jira rejected the action, e.g. because of required fields or an unknown issue type in that project | check project and issue type; ask the AI to adjust the proposal |
| "Invalid issue key." (on a card; for lookups the AI may also report "Invalid page ID.") | wrong format | state the correct key or page ID |
| "Action failed." / "Failed." / "Call failed." | an unexpected error during execution | try again; if it recurs, inform the administration |
| The AI says it cannot find a page that was just created | fresh pages are sometimes not in the search yet | wait briefly or name the page directly |
| After Update Jira issue images, @-mentions, status lozenges or smart links are gone; the description contains [Bild/Anhang] or [gekürzt, … Zeichen gesamt] | the update replaces the whole description; the AI only sees images as the marker [Bild/Anhang] and text beyond about 8,000 characters is cut | check the issue and restore what is missing from the issue history |
Messages for history and archiving
| Message | Cause | Solution |
|---|---|---|
| "History could not be loaded." | the history list was unavailable | reload the page |
| "Conversation could not be loaded." / "Conversation not found." | the conversation was deleted or dropped automatically — 50 conversations are kept per person, the oldest unpinned ones go first | pin or archive the important ones |
| "Fork failed." | the copy could not be created | try again |
| "No personal Confluence space found — open your Confluence profile once ("Create personal space") and try again." | you have no personal Confluence space | open your Confluence profile, create the personal space, archive again |
| "Archiving failed." / "A page with this title already exists." | Confluence unreachable, rights missing, or a title conflict | try again; if it persists, administration |
| Deletion with Save to my Confluence archive first does nothing | archiving failed — then nothing is deleted | fix the archiving cause first, then delete |
| A conversation has disappeared | deleted, temporary, or dropped out of the most recent 50 | not recoverable; prevention: pin or archive |
| Older messages are missing in a long chat | very long conversations are trimmed at the front (the last two messages always stay) | export or archive important content early |
The archive page shows **bold** or tables literally | archive pages are plain text by design | use ↓ Export conversation (Markdown) for a formatted copy |
| The archive page is in English although the interface is German | archive labels follow the Interface language set by the administration — German only if it is set to German (Deutsch) | administration: General Settings |
Messages for your own agents and skills
| Message | Cause | Solution |
|---|---|---|
| "At most 5 own agents." | upper limit reached | edit or delete an existing agent |
| "At most 10 own skills." | upper limit reached | edit or delete an existing skill |
| "The shared registry is full (max 30)." | 30 agents are already shared site-wide. Your agent has been saved as a private agent | reopen it, clear Make available to all users of this site, save again |
| "„…“: name missing or longer than 40 characters." / "„…“: instructions missing." / "„…“: instructions longer than 8000 characters." / "„…“: description longer than 200 characters." / "„…“: emoji longer than 4 characters." | a required field is empty or a limit is exceeded | fill in or shorten the field |
| "„…“: name missing or longer than 60 characters." / "„…“: text missing." / "„…“: text longer than 4000 characters." | skill name or text empty or too long | fill in or shorten |
| "Memory is limited to 4000 characters." | the note is too long | shorten it |
| "Unknown agent for this skill." | the assigned agent no longer exists or is not available to you | choose a different agent or No agent |
| "Save failed." / "Speichern fehlgeschlagen: …" (this German wording also appears in the English interface) / "Delete failed." | the request failed | try again |
| The agent or skill does not appear in the other product | your own agents, skills, memory and history are the same in Jira and Confluence — if something is missing, the product is not connected to the app or the configuration could not be loaded | reload the page or ask your administration; do not create the agent again, it would count against your limit of 5 |
A placeholder such as {{Projét}} is not asked for | placeholders allow only letters A–Z/a–z, the umlauts ä ö ü Ä Ö Ü, ß, digits, spaces, full stops, hyphens and underscores (up to 40 characters) | rename the placeholder |
Messages in the administration
Saving and validation
These English messages appear next to the Save button when a save is rejected. Save on Modules and General saves the whole configuration, including connection cards edited but not yet saved on Connections.
| Message | Cause | Solution |
|---|---|---|
| "Save failed." | validation or saving failed; the exact reason follows | check the entries |
| "Configuration could not be loaded: …" (red alert above the tabs) | the configuration could not be read | reload the page |
| "Add at least one connection." | no connection has been created | create at least one connection |
| "„…“: name missing or longer than 40 characters." | connection name empty or too long | shorten the name |
| "„…“: endpoint must use https://." / "„…“: endpoint is not a valid URL." / ""…": endpoint must be a valid https URL." | the address is faulty | enter the full https address, e.g. https://llm.my-company.com/v1 |
| "„…“: specify at least one model." / "„…“: at most 20 models." / "„…“: invalid model name „…“" | no model, too many models, or a name with invalid characters (allowed: letters, digits, . - _ / :, up to 100 characters) | correct the model list |
| ""…": API key seems too short (at least 8 characters)." | the key entered is too short | paste the complete key |
| "Default model must belong to one of the connections." | the default model refers to a removed connection | choose a model from a saved connection |
| "Site knowledge must be text with at most 4000 characters." | the text is too long | shorten it |
| "At most 8 agents." / "„…“: instructions longer than 8000 characters." | site agents: limit reached or instructions too long | remove an agent or shorten the instructions |
| "At most 30 prompts." / "„…“: text longer than 4000 characters." / ""…": skill references an unknown agent — save the agent first." | templates: limit reached, text too long, or the skill points to an agent that is not saved yet | remove a template, shorten it, or save the agent on Agents first |
| "Web search: endpoint must use https://." / "Web search: an endpoint is required to enable it." / "Web search key seems too short (at least 8 characters)." | web search settings incomplete | complete the address or key — Enabling Web Search and Image Generation |
| "API key deleted — connection is disabled until a new key is saved." | you confirmed Really delete? | enter a new key and save when needed |
| "Delete failed." / "Connection not found." | the key could not be deleted | reload and try again |
Endpoint approvals
| Message | Cause | Solution |
|---|---|---|
| "Network approval for … was declined or failed — nothing was saved." (or "… (code …) — nothing was saved.") | the Atlassian confirmation dialog was declined or cancelled while saving | save again and confirm the dialog |
| "These endpoint domains are configured but not yet approved for this installation: …" (yellow notice on every settings page) | the approval is missing — typical after importing a configuration | click Approve now and confirm the dialog |
| "Approval was declined or failed — these domains stay blocked. Your configuration is unchanged." | the dialog was declined | try again |
| "Customer-managed egress is not available for this installation — these domains stay blocked until it is enabled." / "Saved, but the network approval could not be requested — …" | Atlassian's approval function is not available for this installation; the configuration is saved but every address stays blocked | contact the vendor maplee via your administration |
| "Requests to … were blocked in … although the address appears approved. …" and cells blocked <date> in Approval status per product | the administrator's consent is missing in this product — the domain list is shown installation-wide, but the consent counts per product | click Re-approve in this product and confirm the dialog. A successful Test connection in this product also clears the entry; ordinary chat requests do not |
| "Only Jira administrators may change endpoint approvals. Your account has no Jira admin permission, so the actions on this page are disabled." | you opened the Confluence settings page without Jira admin rights | ask a Jira administrator, or open the settings in Jira |
| "Your Jira admin permission could not be verified from Confluence — the actions stay enabled. …" | the check failed; the actions remain usable | proceed, or use the Jira settings page |
| "The limit of 10 approved domains is reached. …" / "Atlassian allows at most 10 approved domains per installation. …" | at most 10 approved domains per installation | Revoke an unused address or use Replace |
| "Only https is allowed — API keys travel on this connection." / "Not a valid URL." / "This domain is already approved." | the address entered is invalid or already approved | correct the address |
| "Revoking failed — the approval is still in place." / "Re-approving failed or was declined — nothing changed." | the action was declined or failed | try again |
Connection test
| Message | Cause | Solution |
|---|---|---|
| "Connection ok — … model(s) at the endpoint." / "Connection ok." with "Visible for this key: …" | the test succeeded | — |
| "Not in the list (may still work): …" (shown in red although the test succeeded) | a configured model name was not reported by the service | not necessarily an error — test the model in the chat |
| "Test failed." followed by the reason | see the following rows | |
| "Endpoint rejects the API key (401/403)." | key wrong or expired | renew the key |
| "Endpoint responded with HTTP …" | the service reports an error | check address, provider type and quota |
| "Timeout after 10s." | the service did not answer in time | check reachability |
| "Connection failed: … This endpoint needs a network approval: check that an administrator has approved it under Settings → Endpoint approvals." | the address is not reachable or not approved | Managing Endpoint Approvals |
| "The request was blocked inside Atlassian before reaching … — the endpoint is not approved for … yet. …" | the approval is missing in this product; the test records a blocked entry | approve or Re-approve in this product |
| "Connection not found — please save first." / "No API key saved — please set a key and save." / "New — test available after saving." | the connection is not saved yet or has no key | save first, then test |
Messages for web search and image generation
| Message | Cause | Solution |
|---|---|---|
| "Web search is not enabled." | web search is switched off | administration: Enabling Web Search and Image Generation |
| "Web search has no endpoint configured." / "Web search has no API key configured." | the checkbox is ticked but address or key is missing | administration completes the settings |
| "Web search rejects the API key (401/403)." | the key is wrong, expired or was discarded by a service or endpoint switch | enter a new key |
| "Web search rate limit reached (429)." | the search service's quota is exhausted | check the quota with the provider |
| "Web search timed out after 30s." | the search service did not answer in time | check reachability and the approval; with SearXNG also the JSON output format |
| "Web search failed: …" with a note about a network approval | the search address is not approved | Managing Endpoint Approvals |
| The AI never searches the web | the tool is not offered because web search is off or address/key is missing | administration |
| "Image generation is not enabled." / "Image connection not configured." | image generation is off or no image model is selected | administration |
| "The configured image connection type does not support image generation." / the AI never generates images | the image model belongs to an Anthropic connection — it is then silently not offered | use an image model on an OpenAI-compatible or Azure OpenAI connection |
| "Image endpoint responded with HTTP …" | the service reports an error | check model name and quota |
| "Image endpoint returned no URL (b64-only is not supported)." | the service delivers the image in an unsupported form | choose a different image model |
| An image link no longer works | provider image links are often valid only briefly | generate the image again and download it promptly |
Messages in the dashboard gadget
| Message | Cause | Solution |
|---|---|---|
| "Not configured yet — add a question via "Edit"." | no question saved | open the gadget's edit mode and enter a question |
| "Please enter a question." | the field was empty on Save | enter a question |
| "Save failed." | the gadget configuration could not be saved | try again |
| "No answer yet — click "↻ Refresh"." | no answer has been generated | click ↻ Refresh |
| "Gadget could not be loaded." | the app configuration was unavailable | reload the dashboard |
| "Refresh failed." / "Error." | the request could not be started or ended with an unspecified error | click ↻ Refresh again; if it recurs, administration |
| "No response from stream — please try again." | no data arrived for 60 seconds | refresh again |
| "Streaming currently unavailable." | the gadget can only stream | try again later |
| "Hourly limit reached (… requests/hour) — please try again later." | the personal limit of the person who clicked ↻ Refresh | wait |
| "Not configured yet — …" / "The AnyLLM subscription for this site is inactive …" / "This feature has been disabled by your administrator." | administration needed | see The app does not start or is locked |
Common misconfigurations and recovery
| Symptom | Likely cause | Remedy |
|---|---|---|
| Users see Not set up yet although connections exist | no connection has a stored API key | enter the key and save — Setting Up LLM Connections |
| The chat works in Jira but not in Confluence | the endpoint is not approved in Confluence, or Confluence is not connected to the app | approve the endpoint on the Confluence settings page; if the app is missing in Confluence, add Confluence to the installation in Atlassian administration (Jira is the required product; Confluence is added afterwards) |
| After importing a configuration every request fails | the network approval for the imported address is missing | click Approve now in the yellow notice — Managing Endpoint Approvals |
| A model is not found | the model name differs from the service's | Test connection shows the visible model names |
| Users get the first model instead of the default model | the default model belongs to a connection without a key or was removed | choose a default model whose connection has a key — General Settings |
| Answers are noticeably slow | a model with an internal reasoning phase | choose a different default model |
| Answers break off without any text | the response budget is too small for a reasoning model | users: raise Max response tokens or click Reset in ⚙ Model parameters … |
| Usage stays empty | the AI service returns no token usage in its streaming responses | ask the provider whether its streaming API returns usage — Usage Statistics, Import/Export and Backup |
| The web search does not work | the address is not approved, the key is missing, or the key was discarded by a service or endpoint switch | Enabling Web Search and Image Generation |
| Image generation is never offered | the image model is on an Anthropic connection | move it to an OpenAI-compatible or Azure OpenAI connection |
| Users still see disabled surfaces in the menu | platform behaviour — menu entries cannot be hidden per installation | expected; see Modules |
| The chat bar stays visible or hidden for a while after a change | its status is cached in the browser for 10 minutes | wait or clear the site data |
| The settings cannot be opened | missing administration rights | check the rights in the product |
| The approval actions are disabled on the Confluence settings page | no Jira admin permission | use a Jira administrator account |
What you can get back if in doubt
- Configuration: create a ↓ Export as JSON regularly (Import/Export). It contains everything except the API keys — Usage Statistics, Import/Export and Backup.
- API keys: cannot be read out. Keep them where you otherwise manage them.
- Conversations and memory: sit with the individual people and can neither be backed up nor restored centrally. Anyone who wants to keep a chat permanently archives it to Confluence — Managing Chat History.
Contacting support
Turn to your own product administration first — they can view connections, approvals and settings. If the administration has to escalate further, the vendor of the app is maplee; ask your administration for the agreed support routes. This manual deliberately names no addresses or response times.
This information helps — and is safe to share:
- the product (Jira or Confluence) and exactly where you were (e.g. "issue panel", "chat bar", "dashboard gadget")
- the message verbatim
- the time, with time zone
- what you did before it occurred
- whether it is reproducible and whether it affects others too
- whether it occurs in both products
Please never include: API keys, passwords, tokens, complete chat content with confidential data, or personal data of third parties. For diagnosis, the message, the time and the surface are enough.
Related topics
- FAQ — frequently asked questions for users and administrators
- Permissions, Roles and Data Visibility — who may do what and who sees what
- Chatting with the AI · Managing Chat History · Creating Your Own Agents and Skills
- Letting the AI Search, Read and Create in Jira and Confluence — suggestion cards
- AnyLLM in Confluence · AnyLLM in Jira · Dashboard Gadget (AI Report)
- Setting Up LLM Connections · Managing Endpoint Approvals · General Settings · Modules
- Licence, Data Retention and Automatic Deletion
Rendered from the app’s own interface with sample data; the Jira/Confluence frame around it is not shown.
Documentation baseline: app version 0.2.0 · 2026-08-30