github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-08-30 17:25:30 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

[GH-ISSUE #18530] issue: Pipeline events not raised when new chat is created and quickly closed/switched to another chat #34154

New Issue
Closed
opened 2026-04-25 08:04:27 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-04-25 08:04:27 -05:00
Owner
Copy Link
Copy Source

Originally created by @YetheSamartaka on GitHub (Oct 23, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/18530

Check Existing Issues

  • I have searched for any existing and/or related issues.
  • I have searched for any existing and/or related discussions.
  • I am using the latest version of Open WebUI.

Installation Method

Docker

Open WebUI Version

0.6.34

Ollama Version (if applicable)

No response

Operating System

Debian 12

Browser (if applicable)

All

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

Events for pipelines will be activated regardless if the chat was closed before finishing in the background or not.

Actual Behavior

When you open a new chat, put a prompt, send it and open a new chat or close the bar in your browser, events for pipelines are not finished. This can result to incomplete data trace for Langfuse where even tho the chat finishes, those pipelines are reliant on front end parts. This is very wrong and needs to be fixed.

Steps to Reproduce

  1. Have a Langfuse pipeline setup for the Langfuse
  2. Create new chat with some prompt
  3. Quickly switch to a new chat and start new conversation before the first chat finishes
  4. Observe in the langfuse that the trace is not properly finished and a lot of information is missing

Logs & Screenshots

Additional Information

Langfuse 3.121
Pipelines latest version where this commit is the last: https://github.com/open-webui/pipelines/commit/039f9c54f8e9f9bcbabde02c2c853e80d25c79e4

Originally created by @YetheSamartaka on GitHub (Oct 23, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/18530 ### Check Existing Issues - [x] I have searched for any existing and/or related issues. - [x] I have searched for any existing and/or related discussions. - [x] I am using the latest version of Open WebUI. ### Installation Method Docker ### Open WebUI Version 0.6.34 ### Ollama Version (if applicable) _No response_ ### Operating System Debian 12 ### Browser (if applicable) All ### Confirmation - [x] I have read and followed all instructions in `README.md`. - [x] I am using the latest version of **both** Open WebUI and Ollama. - [x] I have included the browser console logs. - [x] I have included the Docker container logs. - [x] I have **provided every relevant configuration, setting, and environment variable used in my setup.** - [x] 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). - [x] 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 Events for pipelines will be activated regardless if the chat was closed before finishing in the background or not. ### Actual Behavior When you open a new chat, put a prompt, send it and open a new chat or close the bar in your browser, events for pipelines are not finished. This can result to incomplete data trace for Langfuse where even tho the chat finishes, those pipelines are reliant on front end parts. This is very wrong and needs to be fixed. ### Steps to Reproduce 1. Have a Langfuse pipeline setup for the Langfuse 2. Create new chat with some prompt 3. Quickly switch to a new chat and start new conversation before the first chat finishes 4. Observe in the langfuse that the trace is not properly finished and a lot of information is missing ### Logs & Screenshots - ### Additional Information Langfuse 3.121 Pipelines latest version where this commit is the last: https://github.com/open-webui/pipelines/commit/039f9c54f8e9f9bcbabde02c2c853e80d25c79e4
GiteaMirror added the bug label 2026-04-25 08:04:28 -05:00
GiteaMirror commented 2026-04-25 08:04:30 -05:00
Author
Owner
Copy Link
Copy Source

@tjbck commented on GitHub (Oct 23, 2025):

For an accurate "tracking" Functions should be used.

<!-- gh-comment-id:3438269179 --> @tjbck commented on GitHub (Oct 23, 2025): For an accurate "tracking" Functions should be used.
GiteaMirror commented 2026-04-25 08:04:30 -05:00
Author
Owner
Copy Link
Copy Source

@YetheSamartaka commented on GitHub (Oct 24, 2025):

Then why are "innacurate" pipelines a thing? Should it be discontinued or marked with some warning?

<!-- gh-comment-id:3441957627 --> @YetheSamartaka commented on GitHub (Oct 24, 2025): Then why are "innacurate" pipelines a thing? Should it be discontinued or marked with some warning?
GiteaMirror commented 2026-04-25 08:04:31 -05:00
Author
Owner
Copy Link
Copy Source

@YetheSamartaka commented on GitHub (Oct 24, 2025):

@tjbck Today I converted the pipeline towards a function and it has the same issue. Otherwise my function is working 1:1 with the pipeline variant. Unfortunately issue will be somewhere else as this is affecting Functions as well.

This is a fundamental architectural limitation of these inlet/outlets - they're designed to run within the request/response lifecycle. When that lifecycle is interrupted by client disconnection, post-processing hooks don't execute. The issue affects all filters that rely on outlet hooks for cleanup, not just Langfuse. A proper fix would require Open WebUI to implement a more robust event system for filter lifecycle management that's decoupled from HTTP connections.

<!-- gh-comment-id:3443676414 --> @YetheSamartaka commented on GitHub (Oct 24, 2025): @tjbck Today I converted the pipeline towards a function and it has the same issue. Otherwise my function is working 1:1 with the pipeline variant. Unfortunately issue will be somewhere else as this is affecting Functions as well. This is a fundamental architectural limitation of these inlet/outlets - they're designed to run within the request/response lifecycle. When that lifecycle is interrupted by client disconnection, post-processing hooks don't execute. The issue affects all filters that rely on outlet hooks for cleanup, not just Langfuse. A proper fix would require Open WebUI to implement a more robust event system for filter lifecycle management that's decoupled from HTTP connections.
GiteaMirror commented 2026-04-25 08:04:31 -05:00
Author
Owner
Copy Link
Copy Source

@YetheSamartaka commented on GitHub (Oct 27, 2025):

@tjbck I looked into that issue further and created a working fix PR:
https://github.com/open-webui/open-webui/pull/18654

<!-- gh-comment-id:3450460875 --> @YetheSamartaka commented on GitHub (Oct 27, 2025): @tjbck I looked into that issue further and created a working fix PR: https://github.com/open-webui/open-webui/pull/18654
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No labels bug
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
GiteaMirror ninjasurge (Kaehlen Rog)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#34154