Events in Open WebUI offer a unique way to interact with users.
You can ask a user to fill out a form generated using an event_call execute() type event or offer them an input form or dropdown field.
But, users may take longer than 60 seconds to answer a question or fill out a field when offered using the event_call feature.
Therefore i am proposing to add an env var which allows admins to configure the timeout for the sio.call() for event_call events so that the event call does not time out after just 60 seconds which causes an Exception in the action or tool using the event call and gives the user more time to actually make a decision or fill out what is shown.
Originally created by @Classic298 on GitHub (Mar 4, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/22220
Events in Open WebUI offer a unique way to interact with users.
You can ask a user to fill out a form generated using an event_call execute() type event or offer them an input form or dropdown field.
But, users may take longer than 60 seconds to answer a question or fill out a field when offered using the event_call feature.
Therefore i am proposing to add an env var which allows admins to configure the timeout for the sio.call() for event_call events so that the event call does not time out after just 60 seconds which causes an Exception in the action or tool using the event call and gives the user more time to actually make a decision or fill out what is shown.
I propose 300s as the new default (5min) which should be sufficient for >90% of usecases where users are asked something by the tool or action and where they need to fill something out, acknowledge something or make a decision with the many event_call type events available and custom ones being able to be built using the execute() type event_call
<!-- gh-comment-id:3997908465 -->
@Classic298 commented on GitHub (Mar 4, 2026):
I propose 300s as the new default (5min) which should be sufficient for >90% of usecases where users are asked something by the tool or action and where they need to fill something out, acknowledge something or make a decision with the many event_call type events available and custom ones being able to be built using the execute() type event_call
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @Classic298 on GitHub (Mar 4, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/22220
Events in Open WebUI offer a unique way to interact with users.
You can ask a user to fill out a form generated using an event_call execute() type event or offer them an input form or dropdown field.
But, users may take longer than 60 seconds to answer a question or fill out a field when offered using the event_call feature.
Therefore i am proposing to add an env var which allows admins to configure the timeout for the sio.call() for event_call events so that the event call does not time out after just 60 seconds which causes an Exception in the action or tool using the event call and gives the user more time to actually make a decision or fill out what is shown.
@Classic298 commented on GitHub (Mar 4, 2026):
https://github.com/open-webui/open-webui/pull/22222
@Classic298 commented on GitHub (Mar 4, 2026):
I propose 300s as the new default (5min) which should be sufficient for >90% of usecases where users are asked something by the tool or action and where they need to fill something out, acknowledge something or make a decision with the many event_call type events available and custom ones being able to be built using the execute() type event_call