#27316·open-webui

issue: Analytics Daily Endpoint fails when to many data

Author: weisser-devCreated Jul 22, 2026Updated Oct 1, 2026
Labelsbugconfirmed issue

Check Existing Issues

  • I have searched for any existing and/or related issues.
  • I have searched for any existing and/or related discussions.
  • I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!).
  • I am using the latest version of Open WebUI.

Installation Method

Docker

Open WebUI Version

0.10.2

Ollama Version (if applicable)

No response

Operating System

windows 11

Browser (if applicable)

No response

Confirmation

  • I have read and followed all instructions in README.md.
  • I am using the latest version of both Open WebUI and Ollama.
  • I have included the browser console logs.
  • I have included the Docker container logs.
  • I have provided every relevant configuration, setting, and environment variable used in my setup.
  • I have clearly listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
  • I have documented step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation. My steps:
  • Start with the initial platform/version/OS and dependencies used,
  • Specify exact install/launch/configure commands,
  • List URLs visited, user input (incl. example values/emails/passwords if needed),
  • Describe all options and toggles enabled or changed,
  • Include any files or environmental changes,
  • Identify the expected and actual result at each stage,
  • Ensure any reasonably skilled user can follow and hit the same issue.

Expected Behavior

That the Data Analytics Daily Endpoint answers correctly and give a valid response

Actual Behavior

When there are to many requests and messages existing, and we call the daily Enpoint, we got a 500 http error code, when we now use timestamp filters, everything works correctly for 30 days... which means we build by our own a solution which asks the endpoint recursively... We run it in k8s

Steps to Reproduce

API Request to the Endpoint via curl + token

Logs & Screenshots

no good logs available just 500er Server Error

Additional Information

No response