Pipeline overriding two simultaneos requests. #124

New Issue

2026-02-15T19:16:05-05:00

yindo commented

2026-02-15 19:16:05 -05:00

Originally created by @Tavernari on GitHub (Sep 21, 2024).

Basically, I have two accounts on my OpenWebUI.
The first account calls my pipeline, then the second account also calls it but the second user responds faster than the first, so the first user also receives the message requested by the second user instead of the user 1 request.
How to avoid that?

My pipeline: https://github.com/Tavernari/openwebui-pipelines/blob/main/o1-reasoning.py

Originally created by @Tavernari on GitHub (Sep 21, 2024). Basically, I have two accounts on my OpenWebUI. The first account calls my pipeline, then the second account also calls it but the second user responds faster than the first, so the first user also receives the message requested by the second user instead of the user 1 request. How to avoid that? My pipeline: https://github.com/Tavernari/openwebui-pipelines/blob/main/o1-reasoning.py

yindo closed this issue

2026-02-15 19:16:05 -05:00

yindo commented

2026-02-15 19:16:05 -05:00

@Tavernari commented on GitHub (Sep 21, 2024):

For future same issue, the problem is because I was saving things on self, and since it shares the instance, it was messing with my algorithm.

@Tavernari commented on GitHub (Sep 21, 2024): For future same issue, the problem is because I was saving things on self, and since it shares the instance, it was messing with my algorithm.

yindo commented

2026-02-15 19:16:06 -05:00

@Panicum commented on GitHub (Sep 23, 2024):

@Tavernari
And how did you manage to fix it and still save some "context" for the users and don't use ".self"/don't mix their conversations?

@Panicum commented on GitHub (Sep 23, 2024): @Tavernari And how did you manage to fix it and still save some "context" for the users and don't use ".self"/don't mix their conversations?

yindo commented

2026-02-15 19:16:06 -05:00