Skip to main content

Error Messages

A reference for the error messages and error pages you may see while using Genie, and what to do about them.

Page-level error screens

These take over the whole browser tab when something fundamental goes wrong.

401 – Unauthorized

You don't have permission to view this page. Please log in to continue.

Cause: You are not signed in, your session expired, or your token was invalidated.

Fix: Click DHL SSO Login to sign in again.

403 – Forbidden

You don't have permission to view this page.

Cause: You are signed in, but you tried to open a page that requires a role you don't have. The most common case is trying to open /create-app or /apps/{id}/edit without admin rights.

Fix: This page is a dead end — it has no buttons. Type genie.dhlrdlab.com/ in the address bar to go back to the landing page. If you believe you should have access, contact the relevant KB owner or Support.

404 – Not Found

The page you are looking for does not exist.

Cause: The URL doesn't match any page in Genie. This can also happen if you try to open a KB you no longer have access to — Genie returns 404 rather than 403 to avoid revealing the KB's existence.

Fix: Click the Go to Home Page button.

Sign-in problems

SymptomLikely causeFix
Stuck on /auth/callback with a spinnerThe SSO redirect didn't completeClear cookies/site data for genie.dhlrdlab.com and retry. If it persists, try a different browser.
MFA prompt rejects every codeAccount-level MFA issueContact IT Service Desk to reset your MFA methods.
"Login failed" toastNetwork blocked Entra during sign-inTry a different network (corporate VPN often required).

Chat errors

These appear inline in the chat as a red error block with a Retry button.

ErrorCauseFix
Your message contains content that was flagged by the OpenAI content filter.Question triggered Azure OpenAI safety filters (e.g., sensitive topic, profanity)Rephrase the question more neutrally.
Your message exceeded the context length limit for this OpenAI model. Please shorten your message or change your settings to retrieve fewer search results.The combination of your current question + chat history is too long for the modelClick New Chat in the sidebar to start a fresh session.
Knowledge base not foundThe KB was deleted while you had it open, or your access was revokedRefresh the page; pick a different KB.
Access deniedYou don't have permission to chat with this KB (you may have been removed)Contact the KB owner.
Generic error messageTransient backend issue, network blipClick Retry. If it persists, wait a minute and try again.
No error, but chat stalls foreverToken expired mid-streamRefresh the page; you'll be redirected to sign in.

Upload errors

These appear as toast notifications when you try to upload a document.

ToastCauseFix
Only PDF files can be uploaded. Please select a PDF file.You picked a non-PDF (Word, Excel, etc.)Convert your file to PDF and try again.
File size exceeds the limit (the exact MB value is whatever the upload zone hint shows, default 100 MB)File is over the active per-file size limit for this environmentCompress the PDF (e.g., reduce image quality) or split it.
File '{name}' already exists in this knowledge baseA file with that exact name is already uploadedRename your file or delete the existing one first.
Upload limit exceeded with details like Cannot upload N files. Current: X/Y files. or Maximum file limit reached (Y files). Please delete some files before uploading new ones.KB has hit its document quotaDelete an unneeded document, or contact Support to raise the limit.
Upload fails with no clear messageNetwork interruption mid-uploadTry again on a more stable connection.

File processing errors

After upload, the document goes through a processing pipeline. Failures show in the document table under the Status column.

Status / messageCauseFix
failed: File rejected: malware detectedAzure Defender flagged the file as maliciousDo not retry. Investigate the file source.
failed: File held: scan inconclusiveMalware scan timed outRetry after a few minutes. Contact Support if it persists.
failed: Extraction failedCorrupted, password-protected, or unusual-format PDFRe-export from the original source; unlock password-protected PDFs first.
failed: Token limit exceededDocument too large/dense for the model contextSplit into smaller PDFs.
failed: (generic)Transient backend errorDelete the failed entry and try uploading again.

Permission and approval errors

SymptomCauseFix
Failed to create join request. You may already have a pending request.You already requested access to this KBCheck My Requests for the status; contact the admin if it's stuck.
You already have access to this knowledge baseYou requested access to a KB you already belong toOpen it from the Apps Dashboard.
Mail service not enabledEmail notifications are off in this environment, so join requests can't fireContact Support; join requests aren't usable until email is configured.
Join request was already processed by another reviewerTwo admins clicked Approve/Reject at the same timeRefresh — the request is already finalised.
Could not retrieve your email address. Please contact support.Microsoft Graph couldn't return your email — usually an account configuration issueContact Support.

Rate limit errors (HTTP 429)

When you exceed a per-action limit, the API returns HTTP 429 with a two-field error body:

  • error: Rate limit exceeded for {action} endpoint
  • message: Please try again in {N} seconds

The frontend may show these together or just one of them, but you'll see a generic chat-error or toast appear. There's no banner or countdown widget. Wait the suggested time and retry.

The most common rate-limited actions: chat (30 per minute), uploads (10 per minute), Knowledge Base writes (5 per minute).

"Generating answer…" never completes

If you've been staring at the spinner for more than 30 seconds:

  1. Check your network — switching from VPN to direct or vice versa can help.
  2. Refresh the page (your sign-in is preserved).
  3. Try a simpler version of your question.
  4. If a specific question always hangs, take note of the wording and Support can investigate.

Reporting a bug

Errors that don't match anything above are likely bugs. When reporting one, please include:

  • What you were trying to do
  • The exact error text (screenshot is ideal)
  • The chat URL (it contains the session ID — /c/{session-id})
  • Your DHL email (so we can match it to logs)

See Contact for how to reach the team.