After a Patient uploads a Health Document, the Processing Agent runs synchronously (awaited inline), but the Wiki Agent and UI Agent run asynchronously via asyncio.ensure_future. If the Patient opens the dashboard immediately after upload, they see stale data (or nothing on first upload).
Make the whole chain synchronous (slower upload response, dashboard always fresh)
Keep async but add a trackable Processing Status the frontend can poll
Context
Found during grill session on CONTEXT.md — the example dialogue implies a fully sequential flow, which doesn't match the actual implementation.
Originally created by @har33sh on GitHub (Apr 29, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/24245
## Problem
After a Patient uploads a Health Document, the Processing Agent runs synchronously (awaited inline), but the Wiki Agent and UI Agent run asynchronously via `asyncio.ensure_future`. If the Patient opens the dashboard immediately after upload, they see stale data (or nothing on first upload).
**Code reference**: `web-ui/backend/open_webui/routers/wiki_lab_reports.py` lines ~270-300
## Options
1. Make the whole chain synchronous (slower upload response, dashboard always fresh)
2. Keep async but add a trackable **Processing Status** the frontend can poll
## Context
Found during grill session on CONTEXT.md — the example dialogue implies a fully sequential flow, which doesn't match the actual implementation.
@pr-validator-bot commented on GitHub (Apr 29, 2026):
⚠️ Missing Issue Title Prefix
@har33sh, your issue title is missing a prefix (e.g., bug:, feat:, docs:).
Please update your issue title to include one of the following prefixes:
bug: Bug report or error you've encountered
feat: Feature request or enhancement suggestion
docs: Documentation issue or improvement request
question: Question about usage or functionality
help: Request for help or support
Example: bug: Login fails when using special characters in password
<!-- gh-comment-id:4346192370 -->
@pr-validator-bot commented on GitHub (Apr 29, 2026):
# ⚠️ Missing Issue Title Prefix
@har33sh, your issue title is missing a prefix (e.g., `bug:`, `feat:`, `docs:`).
Please update your issue title to include one of the following prefixes:
- **bug**: Bug report or error you've encountered
- **feat**: Feature request or enhancement suggestion
- **docs**: Documentation issue or improvement request
- **question**: Question about usage or functionality
- **help**: Request for help or support
Example: `bug: Login fails when using special characters in password`
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 @har33sh on GitHub (Apr 29, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/24245
Problem
After a Patient uploads a Health Document, the Processing Agent runs synchronously (awaited inline), but the Wiki Agent and UI Agent run asynchronously via
asyncio.ensure_future. If the Patient opens the dashboard immediately after upload, they see stale data (or nothing on first upload).Code reference:
web-ui/backend/open_webui/routers/wiki_lab_reports.pylines ~270-300Options
Context
Found during grill session on CONTEXT.md — the example dialogue implies a fully sequential flow, which doesn't match the actual implementation.
@pr-validator-bot commented on GitHub (Apr 29, 2026):
⚠️ Missing Issue Title Prefix
@har33sh, your issue title is missing a prefix (e.g.,
bug:,feat:,docs:).Please update your issue title to include one of the following prefixes:
Example:
bug: Login fails when using special characters in password@Classic298 commented on GitHub (Apr 29, 2026):
????????????????????????????????????????????????????