temporalio / temporalio/temporal

Cannot load archived (s3 provider) workflow history on UI

Open
#6,193 3 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

potential-bug
Dominant language
Go
Stars
23.2k
Forks
1.9k
Avg merge
2d 8h
Merged PRs (30d)
228

Description

From my basic research (with no real context into the code) it seems like DescribeWorkflowExecution in frontend workflow_handler does not take into account that a workflow can be archived. In which case it needs to do special logic.

GetWorkflowExecutionHistory on the other hand, handles archived workflows perfectly.

This results in the UI not being able to show workflow run page because describe request fails with 404.

Expected Behavior

Be able to open a workflow run from Archived page and get the detailed history for history archival.

Actual Behavior

404 on openning the page.

Steps to Reproduce the Problem

  1. Create a namespace with short retention and archival s3 enabled
  2. run a workflow and let archival happen
  3. let retention time pass
  4. try to open workflow from Archived UI page

Specifications

  • Version:
    • Server: 1.23.1
    • UI: 2.27.0
    • Postgres: 14
    • Archival: s3
  • Platform:

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in the frontend workflow_handler at DescribeWorkflowExecution and compare its archived-workflow handling with GetWorkflowExecutionHistory, which already supports archival. Reproduce with a short-retention namespace using S3 archival, then open the workflow from the Archived UI page. Done means the run page loads its detailed history without a 404.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
backend-api-design, distributed-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.