# Archived Workflow are not visible in Temporal WebUI

**URL:** <https://community.temporal.io/t/archived-workflow-are-not-visible-in-temporal-webui/19515>\
**Category:** Community Support\
**Created:** [April 28, 2026, 3:57pm UTC](https://community.temporal.io/t/archived-workflow-are-not-visible-in-temporal-webui/19515 "2026-04-28T15:57:18Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rahul\_Kashyap](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/rahul_kashyap/32/8301_2.png) [@Rahul\_Kashyap](https://community.temporal.io/u/Rahul_Kashyap)\
**Post date:** [April 28, 2026, 3:57pm UTC](https://community.temporal.io/t/archived-workflow-are-not-visible-in-temporal-webui/19515/1 "2026-04-28T15:57:18Z")

</div>

Hi Team,

We have self hosted temporal and enabled the archival on temporal namespace but `Archive` tab does not shows any archived workflows.

Also i can see some open issue around this topic:

> <https://github.com/temporalio/temporal/issues/5624>
>
> \## Expected Behavior
> Viewing the Archival tab for a namespace which has archive…d workflows should display them.
> 
> \## Actual Behavior
> The Archival tab is displaying the message "No Workflows running in this Namespace" even though there are archived workflows present in the configured archival S3 bucket. The GET call to \`api/v1/namespaces/\<namespace\>/archived-workflows?query=\` is failing with an HTTP 400.
> 
> \## Steps to Reproduce the Problem
> 
> 1. Create an S3 bucket for Archival.
> 2. Ensure that Temporal's K8s service account has the below IAM permissions, changing the bucket name here to match.
> \`\`\`
> {
> "Statement": \[
> {
> "Effect": "Allow",
> "Action": \[
> "s3:ListBucket",
> "s3:GetBucketLocation",
> "s3:PutObject",
> "s3:PutObjectAcl",
> "s3:GetObject",
> "s3:GetObjectAcl",
> "s3:DeleteObject"
> \],
> "Resource": \[
> "arn:aws:s3:::temporal-workflow-archive-bucket",
> "arn:aws:s3:::temporal-workflow-archive-bucket/\*"
> \]
> }
> \]
> }
> \`\`\`
> 4. Add the below configuration to the Temporal Helm chart, changing the bucket name here to match.
> \`\`\`
> config:
> archival:
> history:
> state: enabled
> enableRead: true
> provider:
> s3store:
> region: \<aws region\>
> visibility:
> state: enabled
> enableRead: true
> provider: 
> s3store:
> region: \<aws region\>
> 
> namespaceDefaults:
> archival:
> history:
> state: enabled
> URI: s3://temporal-workflow-archive-bucket
> visibility:
> state: enabled
> URI: s3://temporal-workflow-archive-bucket
> \`\`\`
> 5. Turn on archival and visibility for a namespace that has workflows running, and wait for the retention period.
> 6. View the archival bucket and observe that there are files present for those archived workflows.
> 7. Go to the Archival tab for that namespace and observe the message "No Workflows running in this Namespace" and the failed call to \`api/v1/namespaces/\<namespace\>/archived-workflows?query=\`.
> 
> \## Specifications
> 
> - Version: 1.22.5
> - Platform: AWS, EKS, amd64

> <https://github.com/temporalio/temporal/issues/6193>
>
> From my basic research (with no real context into the code) it seems like \`Descr…ibeWorkflowExecution\` 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
> 1. run a workflow and let archival happen 
> 1. let retention time pass
> 2. try to open workflow from Archived UI page
> 
> \## Specifications
> - Version: 
> - Server: 1.23.1
> - UI: 2.27.0
> - Postgres: 14
> - Archival: s3
> - Platform:

Any help regarding this would be appreciated.

 ![Screenshot 2026-04-28 at 9.24.55 PM](https://us1.discourse-cdn.com/flex016/uploads/temporal/original/2X/5/53a3c2b11cf1f1f77b699da3acefc41077f2d957.png)

---

<div class="post-metadata">

**Author:** ![tamara-temporal](https://avatars.discourse-cdn.com/v4/letter/t/e9c0ed/32.png) [@tamara-temporal](https://community.temporal.io/u/tamara-temporal)\
**Post date:** [April 30, 2026, 1:34am UTC](https://community.temporal.io/t/archived-workflow-are-not-visible-in-temporal-webui/19515/2 "2026-04-30T01:34:02Z")

</div>

Rahul:

Thank you for the information. I am going to further investigate. I will update you as I learn more.

Thanks!  
Tamara Henson  
Sr. Dev Support Engineer - Temporal

---

<div class="post-metadata">

**Author:** ![tamara-temporal](https://avatars.discourse-cdn.com/v4/letter/t/e9c0ed/32.png) [@tamara-temporal](https://community.temporal.io/u/tamara-temporal)\
**Post date:** [April 30, 2026, 3:31am UTC](https://community.temporal.io/t/archived-workflow-are-not-visible-in-temporal-webui/19515/3 "2026-04-30T03:31:22Z")

</div>

Rahul:

I wanted to follow up on this. I am unable to reproduce the issue:

 ![Screenshot 2026-04-29 at 8.26.33 PM](https://us1.discourse-cdn.com/flex016/uploads/temporal/original/2X/4/421081abf598de591627260e443041ce503a5245.png)

Can you provide additional information regarding your environment?  
[1] Docker, K8s  
[2] Version  
[3] Storage

Notes: My self hosted is running 2.49.1, in k8s and using Minio.

Thanks!  
Tamara Henson  
Sr. Dev Support Engineer