[DOCS-1700] Update docs for automation history (#1803)

Author: mdlinville

docs.json

@@ -332,6 +332,7 @@
                           "models/automations/create-automations/webhook"
                         ]
                       },
+                      "models/automations/view-automation-history",
                       "models/automations/automation-events"
                     ]
                   },

images/automations/collection-automation-execution-icon.png

@@ -12,15 +12,6 @@ An automation can start when a specific event occurs within a project or registr
 ## Registry
 This section describes the scopes and events for an automation in a [Registry](/models/registry/).
 
-1. Navigate to the W&B Registry at `https://wandb.ai/registry/`.
-1. Click the name of a registry, then view and create automations in the **Automations** tab.
-
-<Frame>
-![Screenshot of the Registry Automations tab with an automation](/images/automations/registry_automations_tab.png)
-</Frame>
-
-Learn more about [creating automations](/models/automations/create-automations/).
-
 ### Scopes
 A [Registry](/models/registry/) automation watches for the event taking place on any collection within a specific registry, including collections added in the future.
 
@@ -32,22 +23,13 @@ A Registry automation can watch for these events:
 ## Project
 This section describes the scopes and events for an automation in a [project](/models/track/project-page/).
 
-1. Navigate to your W&B project on the W&B App at `https://wandb.ai/<team>/<project-name>`.
-1. View and create automations in the **Automations** tab.
-
-<Frame>
-![Screenshot of the Project Automations tab with an automation](/images/automations/project_automations_tab.png)
-</Frame>
-
-Learn more about [creating automations](/models/automations/create-automations/).
-
 ### Scopes
 A project-level automation watches for the event taking place on any collection in the project. Depending on the event you specify, you can further limit the scope of the automation.
 
 ### Artifact events
 This section describes the events related to an artifact that can trigger an automation.
 
-- **A new version is added to an artifact**: Apply recurring actions to each version of an artifact. For example, start a training job when a new dataset artifact version is created. To limit the automation's scope, select a specific artifact in the **Artifact filter** field.
+- **A new version is added to an artifact**: Apply recurring actions to each version of an artifact. For example, start a training job when a new dataset artifact version is created.
 - **An artifact alias is added**: Trigger a specific step of your workflow when a new artifact version in a project has an alias applied that matches the **Alias regex** you specify. For example, run a series of downstream processing steps when an artifact has the `test-set-quality-check` alias applied, or run a workflow each time a new artifact version has the `latest` alias. Only one artifact version can have a given alias at a point in time.
 - **An artifact tag is added**: Trigger a specific step of your workflow when an artifact version in a project has a tag applied that matches the **Tag regex** you specify. For example, specify `^europe.*` to trigger a geo-specific workflow when a tag beginning with the string `europe` is added to an artifact version. Artifact tags are used for grouping and filtering, and a given tag can be assigned to multiple artifact versions simultaneously.
 

images/automations/project_automations_tab.png

@@ -47,6 +47,7 @@ For details, refer to:
 View and manage automations from a project or registry's **Automations** tab.
 
 - To view an automation's details, click its name.
+- To view an automation's execution history, click its name and select the **History** tab. See [View an automation's history](/models/automations/view-automation-history) for details.
 - To edit an automation, click its action `...` menu, then click **Edit automation**.
 - To delete an automation, click its action `...` menu, then click **Delete automation**.
 

images/automations/registry_automations_tab.png

@@ -0,0 +1,66 @@
+---
+title: View an automation's history
+---
+
+<Note>
+This feature requires an Enterprise license. It is available only for:
+- W&B Multi-tenant Cloud
+- W&B Dedicated Cloud
+- W&B Self-Managed v0.75.0+
+</Note>
+
+This page describes how to view and understand the execution history of your W&B [automations](/models/automations), including what triggered an automation, what actions were taken, and whether they succeeded or failed.
+
+Each executed automation generates a record that includes:
+- **Execution timestamp**: When the automation was triggered.
+- **Triggering event**: The specific event triggered the automation.
+- **Status**: The execution's status. See [Execution status](#execution-status).
+- **Action details**: Information about what action was performed, such as notifying a Slack channel or running a webhook.
+- **Result details**: Additional information, if any, about the final outcome of executing the automation, including the error for a failed execution.
+
+Based on your use case, select the **Registry** or **Project** tab for detailed instructions for viewing automation history.
+
+<Tabs>
+<Tab title="Registry">
+1. Navigate to your registry by clicking on **Registry** in the left sidebar.
+1. Select your registry from the list.
+1. View the registry's automations in the **Automations** tab. Click the **Last execution** timestamp to view the execution history details. You can use the search bar to filter by automation name, and you can sort by the last triggered date to find recently executed automations.
+1. View the registry's automation executions in reverse chronological order in the **Automations history** tab, including the event, action, and status. Click an execution timestamp to view details about a particular execution.
+
+<Tip>If a collection has associated automation executions, the icon ![Collection automation execution symbol, a circle with a right-pointing arrow](/images/automations/collection-automation-execution-icon.png) displays, along with the number of associated executions.</Tip>
+</Tab>
+<Tab title="Project">
+1. Click the **Automations** tab in the left navigation. The project's automations display. Click the **Last execution** timestamp to view the execution history details. You can use the search bar to filter by automation name, and you can sort by the last triggered date to find recently executed automations.
+1. In the **History** tab, view all executions of the project's automations in reverse chronological order, starting with the most recent execution. Each execution's metadata displays, including the event, action, and status. Click an execution timestamp to view details about a particular execution.
+</Tab>
+</Tabs>
+
+## Understanding execution details
+
+Each automation execution has one of the following statuses:
+
+- **Finished**: The automation completed all actions successfully.
+- **Failed**: The automation encountered an error and terminated unsuccessfully.
+- **Pending**: The automation is queued for execution.
+
+Click on any execution in the history to view details:
+
+- **Event details**: The specific event that triggered the automation, including:
+  - Event type (e.g., "New artifact version", "Run completed")
+  - Entity information (run ID, artifact name, etc.)
+  - User who triggered the event (if applicable)
+
+- **Action details**: Information about what the automation attempted to do:
+  - Action type (Slack notification or webhook)
+  - Target (Slack channel or webhook URL)
+  - Payload sent (for webhooks)
+
+- **Result information**:
+  - Response status (for webhooks)
+  - Any error messages or stack traces (for failed executions)
+
+## Next steps
+
+- [Create an automation](/models/automations/create-automations)
+- Learn about [Automation events and scopes](/models/automations/automation-events)
+- [Create a secret](/platform/secrets)

models/automations/automation-events.mdx

@@ -189,10 +189,6 @@ Click the **Group** button above the table to group all rows by the value in a p
 ## Automations tab
 Automate downstream actions for versioning artifacts. To create an automation, define trigger events and resulting actions. Actions include executing a webhook or launching a W&B job. For more information, see [Automations](/models/automations/).
 
-<Frame>
-    <img src="/images/automations/project_automations_tab.png" alt="Automation tab"  />
-</Frame>
-
 ## Sweeps tab
 
 Start a new [sweep](/models/sweeps/) from your project.