Skip to main content
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+
This page describes how to view and understand the execution history of your W&B 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.
  • 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.
  • Registry
  • Project
  1. Navigate to your registry by clicking on Registry in the left sidebar.
  2. Select your registry from the list.
  3. 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.
  4. 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.
If a collection has associated automation executions, the icon Collection automation execution symbol, a circle with a right-pointing arrow displays, along with the number of associated executions.

​
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