---
title: "Known issues"
description: "Everything we know is broken right now, which versions it affects, and the workaround where there is one."
url: "https://support.outpostplatform.com/support/known-issues/"
product: "platform"
type: "reference"
status: "draft"
ai_summary: "The Outpost known issues list. One row per open issue with a stable identifier such as KI-0001, the component, the affected versions, a status of Investigating, Confirmed or Fixed, the symptom, the workaround and the date it was last updated. An empty list means nothing is open."
source: "https://gitlab.com/outpostplatform/docs/-/edit/main/src/content/docs/support/known-issues.mdx"
license: "CC BY 4.0"
---

# Known issues

This page lists problems we have confirmed and have not fixed yet. Check it
before you report a bug, and name the identifier when you contact us so that
nobody has to work out which issue you mean.

Every row keeps its identifier for good. `KI-0001` will never mean anything
else, so a link, a ticket or a runbook that cites one stays accurate.

## Open issues

{/*To add an issue, put an object in the array above:

    {
      id: 'KI-0001',
      component: 'Depot',
      versions: '0.3.0 to 0.3.2',
      status: 'Confirmed',
      summary: 'What somebody hitting this sees, in their words.',
      workaround: 'What to do instead. Omit the field when there is none.',
      updated: '2026-09-13',
    }

    Keep the newest first. Statuses are Investigating, Confirmed and Fixed.
    Never reuse an identifier.*/}

## How to read a row

| Column | What it means |
| --- | --- |
| ID | The permanent identifier. Cite this rather than the summary. |
| Component | Which part of Outpost: Depot, Agent, Tray, Remote Outpost or Outpost Sync. |
| Versions | The versions the problem is present in. |
| Status | See below. |
| Issue and workaround | What you see, and what to do meanwhile. |
| Updated | When the row last changed, not when the issue started. |

Three statuses, and they mean different things:

- **Investigating.** We have reproduced it and do not yet know the cause. There
  may be no workaround.
- **Confirmed.** We know the cause and the fix is not shipped.
- **Fixed.** The fix has shipped. The row stays for one release so that
  somebody still on the old version can find it.

## What is not here

- Problems in a preview or release candidate build.
- Anything specific to one deployment. That is a support conversation, not a
  known issue.
- A problem nobody has reported yet. If yours is not on this list,
  [tell us](/support/contact/).

## Related

- [Release notes](/releases/), where fixes are announced with the version that
  carries them.
- [Get help](/support/), for every other channel.