dify - ✅(Solved) Fix Feature: Support workflow_run_id query param for direct log navigation [1 pull requests, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
langgenius/dify#35375Fetched 2026-04-18 05:58:00
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
1
Participants
Timeline (top)
cross-referenced ×1labeled ×1

Currently, the workflow logs page (/app/{appId}/logs) requires manual search to find a specific workflow run. When a workflow execution ID is known (from API responses, error notifications, or monitoring tools), there is no way to navigate directly to that run's logs.

Error Message

Currently, the workflow logs page (/app/{appId}/logs) requires manual search to find a specific workflow run. When a workflow execution ID is known (from API responses, error notifications, or monitoring tools), there is no way to navigate directly to that run's logs.

Root Cause

Currently, the workflow logs page (/app/{appId}/logs) requires manual search to find a specific workflow run. When a workflow execution ID is known (from API responses, error notifications, or monitoring tools), there is no way to navigate directly to that run's logs.

Fix Action

Fixed

PR fix notes

PR #34951: Support workflow_run_id query param on workflow logs page

Description (problem / solution / changelog)

Summary

Supports passing workflow_run_id via the workflow logs URL for faster lookup.

Example:

  • /app/<appId>/logs?workflow_run_id=<runId>

This change:

  • initializes the workflow logs search input from workflow_run_id
  • triggers the existing keyword-based log lookup automatically
  • keeps workflow_run_id in sync when the keyword changes
  • clears stale page from the URL when the keyword changes

Scope

This PR is intentionally narrow:

  • no backend/API changes
  • no new query params beyond workflow_run_id
  • no changes to workflow log pagination behavior
  • no auto-opening of a log detail drawer from URL state

Why no backend change

The existing workflow logs backend already supports matching workflow run IDs through the current keyword search path, so this PR only adds the missing URL/state wiring on the frontend.

Validation

Ran:

  • pnpm -C web test -- --run app/components/app/workflow-log/__tests__
  • pnpm -C web test -- --run app/components/app/log/__tests__
  • pnpm -C web test -- --run app/components/app/log-annotation/__tests__

Notes

This PR supports URL-based initialization of the workflow log search from workflow_run_id.

It does not try to implement full post-mount URL/state synchronization for every possible navigation case. I kept that out of scope to keep the first contribution small and aligned with the issue request.

Changed files

  • web/app/components/app/workflow-log/__tests__/index.spec.tsx (modified, +52/-0)
  • web/app/components/app/workflow-log/index.tsx (modified, +61/-5)
RAW_BUFFERClick to expand / collapse

Summary

Currently, the workflow logs page (/app/{appId}/logs) requires manual search to find a specific workflow run. When a workflow execution ID is known (from API responses, error notifications, or monitoring tools), there is no way to navigate directly to that run's logs.

Use Case

  • A user receives a workflow_run_id from a webhook, alert, or API response
  • They want to immediately inspect that specific run in the logs UI
  • Currently they must manually search or scroll

Proposed Solution

Support passing workflow_run_id as a URL query parameter to pre-populate the search and trigger the lookup automatically: /app/<appId>/logs?workflow_run_id=<runId>

This follows the same URL-state pattern already used by other parts of the UI (e.g., page param).

Implementation

PR #34951 implements this feature. Changes are additive only — no existing behavior changed:

  • Initializes the keyword search input from workflow_run_id URL param
  • Auto-triggers the existing keyword-based lookup
  • Keeps workflow_run_id in sync when the keyword changes
  • Clears stale page from URL when keyword changes

Impact

Low risk — frontend only, no backend/API changes needed. Tested with the existing log lookup flow.

Opening this issue per @lyzno1's request on PR #34951.

extent analysis

TL;DR

Passing the workflow_run_id as a URL query parameter to the workflow logs page can enable direct navigation to a specific workflow run's logs.

Guidance

  • Review PR #34951 to understand the implementation details of the proposed solution.
  • Test the new feature by passing a valid workflow_run_id as a URL query parameter to the workflow logs page, e.g., /app/<appId>/logs?workflow_run_id=<runId>.
  • Verify that the keyword search input is pre-populated with the workflow_run_id and the lookup is triggered automatically.
  • Check that the workflow_run_id remains in sync when the keyword changes and that the page parameter is cleared from the URL when the keyword changes.

Example

No code snippet is provided as the issue does not require a code-level solution, but rather a review and testing of the proposed PR #34951.

Notes

The proposed solution is considered low risk and additive only, with no changes to existing behavior. However, thorough testing is still necessary to ensure the new feature works as expected.

Recommendation

Apply the workaround by passing the workflow_run_id as a URL query parameter to the workflow logs page, as this provides a direct solution to the problem and follows the existing URL-state pattern used by other parts of the UI.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING