---
category: [Administration & Integrations, Administration & Integrations/Custom Integrations & Apps, Platform and Product Extensions, Platform and Product Extensions/Integration]
nav: wcp_docs
parent_url: /wcp_docs/
title: >- 
  Concept: Orchestration Activity
layout: subsection
---

The <b>Orchestration Activity</b> dashboard on an app's home page enables you to monitor, manage, and analyze the orchestrations associated with that app in real time.

<b>Note:</b> Orchestrations are displayed here only when they have been run on a tenant.

The main <b>Orchestration Activity</b> table provides an overview of runs for every orchestration in this app that has been executed. You can click on an orchestration to view a table showing more detailed information about its individual run instances. The main table displays this information:

<table><thead><tr><th>Heading</th><th>Description</th></tr></thead><tbody><tr><td><b>Orchestration</b></td><td>The orchestration's name. <p>Click to view all instances of the orchestration's runs.</p></td></tr><tr><td><b>Latest Run</b></td><td>The unique instance ID of the orchestration's latest run. <p>Click to view all instances of the orchestration's runs.</p></td></tr><tr><td><b>Summary of Runs</b></td><td>A graphical overview of all the orchestration's runs, color-coded by status: <ul><li>Green: Completed.
</li><li>Yellow: Completed with errors.
</li><li>Red: Failed, timed out, or cancelled.
</li><li>Blue: Currently running or awaiting callback.
</li></ul> <p>To see the specific numbers behind the graphical overview, expand the cell contents. </p></td></tr><tr><td><b>Tenant of Latest Run</b></td><td>The name of the tenant where the latest run was performed. <p>Click to open the tenant's sign-in page.</p></td></tr><tr><td><b>Actions</b></td><td>Open the orchestration in Orchestration Builder.</td></tr></tbody></table><br/>

To limit the number of orchestrations included in the table, click the <b>Filter</b> button. You can select a <b>Date Range</b> and include only those orchestrations that started within that range, only those that ended within it, or both.

You can also choose to include only those orchestrations that ran on a particular <b>Tenant</b> and only those with runs that failed.

The combination of date, tenant, and run success criteria enables you to filter for a wide variety of scenarios. Example: you can choose to view only those orchestrations that had successful runs on a particular tenant that ended in the last 12 hours.

To view activity information for a particular orchestration, or to kill or cancel it, click its name in the <b>Orchestration Activity</b> table.The table for a single orchestration shows this information:

<table><thead><tr><th>Heading</th><th>Description</th></tr></thead><tbody><tr><td><b>Run ID</b></td><td>The unique instance ID of this run. This ID is useful for correlating logs, troubleshooting issues, and analyzing performance metrics. <p>Expand the cell to view and copy these additional useful IDs:</p><ul><li>Common Request ID: A unique identifier for the request that initiated the orchestration run. This ID is useful for tracing the origin of the orchestration run and correlating it with other related logs and requests across services.
</li><li>Process ID: Unique identifiers for each of the sequential processes within the orchestration run. These IDs are useful for debugging and performance analysis.
</li></ul></td></tr><tr><td><b>Current Status</b></td><td>Expand the cell to view additional information on the run's status and to access associated logs. <p>An orchestration can have any of these statuses:</p><ul><li>RUNNING: The orchestration is currently in progress.
</li><li>AWAITING_CALLBACK: The orchestration is paused and waiting for an external callback to proceed.
</li><li>SUCCESS: The orchestration completed successfully.
</li><li>CANCELLED: The orchestration was cancelled before completion.
</li><li>KILLED: The orchestration was killed before completion.
</li><li>COMPLETED_WITH_ERROR: The orchestration completed but encountered processing errors.
</li><li>QUEUED: The orchestration is queued and waiting to be executed.
</li><li>TIMED_OUT: The orchestration did not complete within the expected time frame.
</li><li>FAILED: The orchestration failed to complete successfully.
</li></ul> <p>Click <b>View Logs</b>, when the option is available, to navigate to the <b>Logs</b> tab on the <b>Analytics</b> dashboard. The relevant filter for the orchestration will have been applied. For more information, see <a href="/wcp_docs/hlt1558652308211.html">Reference: Application Logs</a> .</p></td></tr><tr><td><b>Start Time</b></td><td>The timestamp when the orchestration run started. Expand the cell to view and copy these additional metrics: <ul><li>Elapsed Time: The total duration from the moment the orchestration run starts to the moment it completes. It includes all the time taken for the orchestration to execute, including any waiting periods, delays, or external dependencies.
</li><li>Compute Time: The sum of the actual processing times of all the steps within the orchestration run. It only includes the time spent actively executing the steps and processes, excluding any waiting periods or delays.
</li></ul></td></tr><tr><td><b>Tenant</b></td><td>The name of the tenant where this run was performed. <p>Click to open the tenant's sign-in page.</p></td></tr></tbody></table><br/>

You can also <b>Filter</b> the orchestration runs displayed in the <b>Instances</b> table. As with the main <b>Orchestration Activity</b> table, you can limit your view to a <b>Date Range</b> and a particular <b>Tenant</b>.

You can also filter by run <b>Status</b> and, under <b>Other IDs</b>, by <b>Common Request ID</b> or <b>Instance ID</b>.

<b>Cancelling or Killing an Orchestration</b>

To cancel or kill an orchestration, select its name in the <b>Orchestration Activity</b> table.

When you select <b>Cancel</b>, Orchestrate identifies the next safe cancellation checkpoint that you defined in the orchestration flow. When it reaches that point, it cleans up resources and gracefully terminates the orchestration with the status "Cancelled".

Cancellation is a careful, orderly process, designed to ensure data consistency between systems. However, there are some circumstances in which you might want to stop an orchestration immediately, regardless of the potential for data inconsistency. Example: an orchestration might get stuck in an infinite loop that never reaches a cancellation checkpoint. Those circumstances require a forceful termination mechanism that bypasses standard cancellation logic and stops execution instantly. This is known as killing an orchestration.

When you select <b>Kill Orchestration</b>, Orchestrate invites you to consider cancelling as a first resort. If you click <b>Kill Anyway</b>, you're asked to enter a confirmation phrase before finally clicking <b>Kill Orchestration</b>. Your orchestration terminates immediately with the status "Killed".

### Related Information

[Concept: Orchestration Processes](/wcp_docs/GUID-3274e8db-46ed-4c0b-bedc-e36948e26613.html)