# Archive showing irrelevant "temporal-sys-worker-deployment" workflows

**URL:** <https://community.temporal.io/t/archive-showing-irrelevant-temporal-sys-worker-deployment-workflows/19877>\
**Category:** Community Support\
**Tags:** general-impl\
**Created:** [October 30, 2026, 9:54am UTC](https://community.temporal.io/t/archive-showing-irrelevant-temporal-sys-worker-deployment-workflows/19877 "2026-10-30T09:54:41Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jsrolon](https://avatars.discourse-cdn.com/v4/letter/j/c0e974/32.png) [@jsrolon](https://community.temporal.io/u/jsrolon)\
**Post date:** [October 30, 2026, 9:54am UTC](https://community.temporal.io/t/archive-showing-irrelevant-temporal-sys-worker-deployment-workflows/19877/1 "2026-10-30T09:54:41Z")

</div>

Hello, I’m running a self-hosted temporal instance on Kubernetes, deployed with the Helm chart version 1.7.0 ( [GitHub - temporalio/helm-charts at ab89869a913207bd191e60a90193512bd9adcb80 · GitHub](https://github.com/temporalio/helm-charts/tree/ab89869a913207bd191e60a90193512bd9adcb80) ) which uses server image version 1.32.0.

I’ve just enabled the archiving feature for the first time, using a filesystem-backed store. When I go to the archival page, I am seeing a very large amount of `temporal-sys-worker-deployment` and `temporal-sys-worker-deployment-version` workflows.

 ![image](https://us1.discourse-cdn.com/flex016/uploads/temporal/original/2X/a/ae5e6eddc937edb2469befa3a51d9f7279a2f6f6.png)

From their name, I originally thought they were triggered in the `temporal-system` namespace, so I disabled archival in that namespace. But they aren’t. They seem to be hidden workflows in the `default` namespace. They don’t show up in the normal web workflow view, nor when running `temporal workflow list`.

I don’t want to archive these workflows since they’re completely irrelevant to me, and they’re taking up space in my archive. Can they be disabled somehow?

---

<div class="post-metadata">

**Author:** ![tihomir](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/tihomir/32/6580_2.png) [@tihomir](https://community.temporal.io/u/tihomir)\
**Post date:** [October 30, 2026, 3:44pm UTC](https://community.temporal.io/t/archive-showing-irrelevant-temporal-sys-worker-deployment-workflows/19877/2 "2026-10-30T15:44:28Z")

</div>

Yeah those are not workflows that you started but they are internal workflows server uses for Worker Versioning.

When your sdk worker polls with worker deployment option set (deployment name and build id)  
server starts 2 internal workflows in that workers namespace.  
You cant really see those with normal visibility list query cause they are behind

`TemporalNamespaceDivision = 'TemporalWorkerDeployment'`

so youd have to do something like

`temporal workflow list --query "TemporalNamespaceDivision = 'TemporalWorkerDeployment'"`

Why so many runs, well those workflows ContinueAsNew after pretty much any change like worker registering, setting current or ramp version and things like that.

You cannot currently in OSS exclude them from being archived unfortunately.  
Will need a custom archiver impl to do that. You can see sample that does this [here](https://github.com/tsurdilo/my-temporal-dockercompose/tree/main/server/archiver) if helps - look at the `excludeWorkflowIDPrefixes` section in the readme and the dir has also impl you can follow.

Created issue for it - [Archival can’t skip the server internal workflows in user namespaces (for example Worker Deployment workflows) · Issue #12838 · temporalio/temporal · GitHub](https://github.com/temporalio/temporal/issues/12838)