diff --git a/public/docs/img/bolt-slash.svg b/public/docs/img/bolt-slash.svg
new file mode 100644
index 0000000000..80ca5829b9
--- /dev/null
+++ b/public/docs/img/bolt-slash.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/src/pages/docs/argo-cd/live-object-status/index.md b/src/pages/docs/argo-cd/live-object-status/index.md
index 6f3156a982..5b3a29f4ea 100644
--- a/src/pages/docs/argo-cd/live-object-status/index.md
+++ b/src/pages/docs/argo-cd/live-object-status/index.md
@@ -1,7 +1,7 @@
---
layout: src/layouts/Default.astro
pubDate: 2025-03-28
-modDate: 2026-03-16
+modDate: 2026-03-19
navSection: Live Object Status
title: Argo CD Live Object Status
navTitle: Live Object Status
@@ -45,15 +45,16 @@ Octopus populates the Live Status Table with content taken directly from Argo.
The project health status is a roll-up of the health of all objects:
-| Label | Status Icon | Description |
-| :---------- | :------------------------------------------------: |:-------------------------------------------------------------------------------------------------------------------------|
-| Progressing | | One or more objects of the mapped application are in a progressing state |
-| Healthy | | The objects in the cluster match that specified in the applications’ source git repositories, and are executing correctly|
-| Unknown | | We’re having trouble getting live status updates for this application |
-| Degraded | | Your objects experienced errors after the deployment completed |
-| Missing | | One or more desired objects are missing from the cluster |
-| Unavailable | | Application live status is unavailable because your last deployment failed |
-| Waiting | | Application live status will be available once the deployment completes |
+| Label | Status Icon | Description |
+| :---------- | :------------------------------------------------------------------------------: |:-------------------------------------------------------------------------------------------------------------------------|
+| Progressing | | One or more objects of the mapped application are in a progressing state |
+| Healthy | | The objects in the cluster match that specified in the applications’ source git repositories, and are executing correctly|
+| Unknown | | We’re having trouble getting live status updates for this application |
+| Degraded | | Your objects experienced errors after the deployment completed |
+| Missing | | One or more desired objects are missing from the cluster |
+| Unavailable | | Application live status is unavailable because your last deployment failed |
+| Waiting | | Application live status will be available once the deployment completes |
+| Stale | | Status information is stale. No data has been received in the last 10 minutes |
### Project Sync Status
@@ -68,18 +69,26 @@ Sync Status tracks whether the changes Octopus pushed to git still match what Ar
| Unavailable | | Application sync status is unavailable because your last deployment failed |
| Waiting | | Application sync status will be available once the deployment completes |
-### Object status
-
-| Label | Status Icon | Description |
-| :---------- | :-------------------------------------------: |:------------------------------------------------------------------------------------------------------------|
-| Progressing | | Object is attempting to reach the desired state |
-| Healthy | | Object is in sync and reporting that it is running as expected |
-| Unknown | | We don't have information about the live status of this object |
-| Degraded | | Object has run into a problem, check the logs or events to find out more |
-| Out of Sync | | Object manifest in the cluster is different from that specified in the Argo CD application's git repository |
-| Missing | | Object is missing from the cluster |
-| In Sync | | Object manifest matches what was applied, but does not report any additional health status |
-| Suspended | | Job is not currently running |
+### Object Health Status
+
+| Label | Status Icon | Description |
+| :---------- | :------------------------------------------------------------------------------: |:------------------------------------------------------------------------------|
+| Progressing | | Object is attempting to reach the desired state |
+| Healthy | | Object is in sync and reporting that it is running as expected |
+| Unknown | | We don't have information about the live status of this object |
+| Degraded | | Object has run into a problem, check the logs or events to find out more |
+| Missing | | Object is missing from the cluster |
+| Suspended | | Job is not currently running |
+| Stale | | Status information is stale. No data has been received in the last 10 minutes |
+
+### Object Sync Status
+
+| Label | Status Icon | Description |
+| :---------- | :-------------------------------------------: |:-----------------------------------------------------------------------------------------------------------------------------|
+| In Sync | | Argo CD reports the object is synced and the git configuration still matches what Octopus last applied |
+| Out of Sync | | Argo CD has detected that the desired state in the cluster differs from the application’s git repository. |
+| Git Drift | | Octopus has detected that the changes it applied to git have been modified since the last deployment (e.g. by a manual edit) |
+| Unknown | | We don't have information about the live status of this object |
### Detailed object information
diff --git a/src/pages/docs/kubernetes/live-object-status/index.md b/src/pages/docs/kubernetes/live-object-status/index.md
index 0b48e58108..2b08a0a755 100644
--- a/src/pages/docs/kubernetes/live-object-status/index.md
+++ b/src/pages/docs/kubernetes/live-object-status/index.md
@@ -1,7 +1,7 @@
---
layout: src/layouts/Default.astro
pubDate: 2025-03-28
-modDate: 2025-05-16
+modDate: 2026-03-19
navSection: Live Object Status
title: Kubernetes Live Object Status
navTitle: Overview
@@ -38,31 +38,52 @@ Octopus display individual status at an object level as well as summarized statu
:::
-### Application status
+### Application Health Status
+
+The application health status is a roll-up of the health of all objects:
+
+| Label | Status Icon | Description |
+| :---------- | :----------------------------------------------------------------------------------: | :-------------------------------------------------------------------------- |
+| Progressing | | Objects in your application are currently in a progressing state |
+| Healthy | | The objects in your cluster match what was specified in the last deployment |
+| Unknown | | We're having trouble getting live status updates for this application |
+| Degraded | | Your objects experienced errors after the deployment completed |
+| Missing | | Objects in your application are currently in a missing state |
+| Unavailable | | Application live status is unavailable because your last deployment failed |
+| Waiting | | Application live status will be available once the deployment completes |
+| Stale | . | Status information is stale. No data has been received in the last 10 minutes|
+
+### Application Sync Status
+
+Sync Status tracks whether the changes Octopus deployed still matches the resources in the cluster.
| Label | Status Icon | Description |
-| :---------- | :------------------------------------------------: | :-------------------------------------------------------------------------- |
-| Progressing | | Objects in your application are currently in a progressing state |
-| Healthy | | The objects in your cluster match what was specified in the last deployment |
-| Unknown | | We're having trouble getting live status updates for this application |
-| Degraded | | Your objects experienced errors after the deployment completed |
+| :---------- | :------------------------------------------------: |:----------------------------------------------------------------------------|
+| In Sync | | The objects on your cluster match what you last deployed |
| Out of Sync | | The objects on your cluster no longer match what you last deployed |
-| Missing | | Objects in your application are currently in a missing state |
-| Unavailable | | Application live status is unavailable because your last deployment failed |
-| Waiting | | Application live status will be available once the deployment completes |
-
-### Object status
-
-| Label | Status Icon | Description |
-| :---------- | :-------------------------------------------: | :----------------------------------------------------------------------------------------- |
-| Progressing | | Object is attempting to reach the desired state |
-| Healthy | | Object is in sync and reporting that it is running as expected |
-| Unknown | | We don't have up-to-date information about the live status of this object |
-| Degraded | | Object has run into a problem, check the logs or events to find out more |
-| Out of Sync | | Object manifest is not the same as what was applied |
-| Missing | | Object is missing from the cluster |
-| In Sync | | Object manifest matches what was applied, but does not report any additional health status |
-| Suspended | | Job is not currently running |
+| Unknown | | We’re having trouble getting sync status updates for this application |
+| Unavailable | | Application sync status is unavailable because your last deployment failed |
+| Waiting | | Application sync status will be available once the deployment completes |
+
+### Object Health Status
+
+| Label | Status Icon | Description |
+| :---------- | :-------------------------------------------------------------------------------: |:-------------------------------------------------------------------------------|
+| Progressing | | Object is attempting to reach the desired state |
+| Healthy | | Object is in sync and reporting that it is running as expected |
+| Unknown | | We don't have information about the live status of this object |
+| Degraded | | Object has run into a problem, check the logs or events to find out more |
+| Missing | | Object is missing from the cluster |
+| Suspended | | Job is not currently running |
+| Stale | | Status information is stale. No data has been received in the last 10 minutes |
+
+### Object Sync Status
+
+| Label | Status Icon | Description |
+| :---------- | :-------------------------------------------: |:-----------------------------------------------------------------|
+| In Sync | | Object manifest matches what was applied |
+| Out of Sync | | Object manifest is not the same as what was applied |
+| Unknown | | We don't have information about the live status of this object |
Take a look at our [troubleshooting guide](/docs/kubernetes/live-object-status/troubleshooting) for details on why you may see some object statuses
| Status information is stale. No data has been received in the last 10 minutes |
### Project Sync Status
@@ -68,18 +69,26 @@ Sync Status tracks whether the changes Octopus pushed to git still match what Ar
| Unavailable | | Application sync status is unavailable because your last deployment failed |
| Waiting | | Application sync status will be available once the deployment completes |
-### Object status
-
-| Label | Status Icon | Description |
-| :---------- | :-------------------------------------------: |:------------------------------------------------------------------------------------------------------------|
-| Progressing | | Object is attempting to reach the desired state |
-| Healthy | | Object is in sync and reporting that it is running as expected |
-| Unknown | | We don't have information about the live status of this object |
-| Degraded | | Object has run into a problem, check the logs or events to find out more |
-| Out of Sync | | Object manifest in the cluster is different from that specified in the Argo CD application's git repository |
-| Missing | | Object is missing from the cluster |
-| In Sync | | Object manifest matches what was applied, but does not report any additional health status |
-| Suspended | | Job is not currently running |
+### Object Health Status
+
+| Label | Status Icon | Description |
+| :---------- | :------------------------------------------------------------------------------: |:------------------------------------------------------------------------------|
+| Progressing | | Object is attempting to reach the desired state |
+| Healthy | | Object is in sync and reporting that it is running as expected |
+| Unknown | | We don't have information about the live status of this object |
+| Degraded | | Object has run into a problem, check the logs or events to find out more |
+| Missing | | Object is missing from the cluster |
+| Suspended | | Job is not currently running |
+| Stale |