> For the complete documentation index, see [llms.txt](https://docs.complycube.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.complycube.com/documentation/product-guides/compliance-studio/workflows/workflow-sessions-and-results.md).

# Workflow sessions and results

Start and monitor customer verification sessions, review KYC and KYB results, and track onboarding performance through the Portal, API, and webhooks.

### Workflow sessions overview <a href="#toc_2" id="toc_2"></a>

A **workflow** defines a verification journey. A **workflow session** is one customer's instance of that journey, recording their progress, submitted information, verification checks, policy evaluations, and activity.

Use sessions to understand **what the customer completed**, **what each check found**, and **how the overall outcome was decided**. Each session retains the workflow version it started with, so your team can review the configuration used for that verification.

<figure><img src="https://1615271746-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKyFKMqftsmT6qln9zo5y%2Fuploads%2FYSPWpWywSKWachxN5qvi%2Fworkflow_session.png?alt=media&amp;token=4f8e3b49-054f-4bfc-94c0-937e86f291ec" alt=""><figcaption><p>Workflow Session - Results summary view.</p></figcaption></figure>

### Starting sessions <a href="#toc_3" id="toc_3"></a>

Choose how customers enter a workflow according to your integration and the checks it contains.

<table><thead><tr><th width="240.65234375">Method</th><th>How it is used</th></tr></thead><tbody><tr><td><a href="https://docs.complycube.com/documentation/quick-guides/web-portal-quick-guide/send-verification-link-workflows.md">Web Portal</a></td><td>Send a verification link to the customer.</td></tr><tr><td><a href="https://docs.complycube.com/documentation/quick-guides/hosted-solution-quick-guide.md">Hosted Solution</a></td><td>Direct the customer to a hosted verification journey.</td></tr><tr><td><a href="https://docs.complycube.com/documentation/quick-guides/web-sdk-quick-guide.md">Web SDK</a></td><td>Present supported verification steps within your web application.</td></tr><tr><td><a href="https://docs.complycube.com/documentation/quick-guides/mobile-sdk-guide.md">Mobile SDKs</a></td><td>Present supported verification steps within your mobile application.</td></tr><tr><td><a href="https://docs.complycube.com/documentation/product-guides/compliance-studio/lifecycle-triggers.md">Lifecycle Triggers</a></td><td>Send workflows automatically for periodic reviews, document renewal, and other configured follow-up.</td></tr><tr><td><a href="https://docs.complycube.com/documentation/api-reference/core-resources/workflow-sessions.md">API</a></td><td>Create and manage sessions through your integration.</td></tr></tbody></table>

### Session tracking <a href="#toc_4" id="toc_4"></a>

Workflow sessions can be monitored in real time through the ComplyCube Portal. The Portal provides full visibility into each customer’s verification journey, making it easy to track progress, identify issues, and manage outcomes.

Open the relevant **workflow session** in the Portal to review the customer's progress and verification evidence. You can:

* **Review session details**: Inspect completed steps, submitted information, uploaded documents, and captured biometrics.
* **Monitor verification checks**: Follow checks as they move through processing and review their results.
* **Track session state**: See whether the journey is Started, Processing, Complete, Abandoned, or Cancelled.
* **Audit trails**: Access timestamps and metadata for compliance and internal review.
* **Inspect the original configuration**: Open **Flow setup** to see the workflow version used, including its outcome rules, result actions, and case configuration.

<figure><img src="https://1615271746-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKyFKMqftsmT6qln9zo5y%2Fuploads%2FAtcS2WKiIR1I2OSsl96X%2Fworkflow_session_activity.png?alt=media&amp;token=a0372bdc-d20b-4684-a4c3-aebde5736f79" alt=""><figcaption><p>Workflow Session - Activities timeline view.</p></figcaption></figure>

#### Workflow version used by a session <a href="#toc_5" id="toc_5"></a>

Existing sessions remain on the **workflow version they started with**. Activating a newer version does not update sessions already in progress.

To move a customer who has already started a verification journey to a **new workflow version**, first **cancel their incomplete session**, then **start a new session** using the updated version. The customer will need to complete the journey **from the beginning**.

Use **Flow setup** to inspect the configuration used by a session, including when investigating results or comparing behavior between versions.

### Session lifecycle <a href="#toc_6" id="toc_6"></a>

A workflow session represents the customer’s progress through a verification journey. Each session moves through a defined lifecycle, with its status reflecting the customer’s activity and the processing state.

<table><thead><tr><th width="159.94140625">State</th><th width="344.19140625">Description</th><th>Can the customer resume?</th></tr></thead><tbody><tr><td><strong>Started</strong></td><td>The customer has initiated the journey and has not yet submitted it for processing. They can return after leaving the page, refreshing, or closing the app.</td><td><strong>Yes</strong>, while the session remains Started.</td></tr><tr><td><strong>Processing</strong></td><td>The customer has submitted information and one or more verification checks are running.</td><td>The customer-facing journey has been submitted.</td></tr><tr><td><strong>Complete</strong></td><td>All verification checks have finished. Results are available through the Portal and API, with webhook notifications.</td><td>No further customer action is required.</td></tr><tr><td><strong>Abandoned</strong></td><td>The journey was left incomplete for an extended period.</td><td><strong>No</strong>. Start a new session.</td></tr><tr><td><strong>Cancelled</strong></td><td><p>The session was explicitly cancelled before completion, typically by an administrative action by you or a team member.</p><h4 id="session-results"><br></h4></td><td><strong>No</strong>. Start a new session.</td></tr></tbody></table>

{% hint style="info" %}
**State and outcome are separate.** A session can be **Complete** while its outcome is **Attention**, meaning verification has finished but the result still requires review.
{% endhint %}

### Session results <a href="#toc_7" id="toc_7"></a>

Session results bring together **individual check outcomes**, **policy evaluations**, and the **overall verification decision**. Review them alongside the supporting evidence and activity history.

<figure><img src="https://1615271746-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKyFKMqftsmT6qln9zo5y%2Fuploads%2FuxqA1P9EBu4KNYghBmz6%2Fworkflow_session_results.png?alt=media&amp;token=05104c7c-3143-4df8-95c4-9d9bb75c6bf7" alt=""><figcaption><p>Workflow Session - Verification result breakdown.</p></figcaption></figure>

The overall session outcome is **Clear**, **Attention**, or **Rejected**. It can be determined by configured outcome rules or ComplyCube's default decision behavior, with compliance policies and manual review also affecting the final result.

#### Default session result <a href="#toc_8" id="toc_8"></a>

When no outcome rule matches, or outcome rules are disabled, ComplyCube uses the default session result.

| Condition                                                                | Default outcome | Meaning                                                                                      |
| ------------------------------------------------------------------------ | --------------- | -------------------------------------------------------------------------------------------- |
| All checks and policies return **Clear**.                                | **Clear**       | No issues were identified by those checks and policies.                                      |
| Any check or policy returns **Attention**.                               | **Attention**   | The session requires manual review.                                                          |
| Any check is **Not processed**.                                          | **Attention**   | The unprocessed check needs to be resolved.                                                  |
| A reviewer **rejects** a check.                                          | **Rejected**    | A check has been rejected through review.                                                    |
| A screening match is **confirmed** as a sanctions or watchlist match.    | **Rejected**    | The confirmed screening finding results in rejection.                                        |
| A match of another type, such as PEP or adverse media, is **confirmed**. | **Attention**   | The outcome remains Attention unless a team member explicitly overrides the session outcome. |

#### Outcome rules and reviewer decisions <a href="#toc_9" id="toc_9"></a>

**Outcome rules** evaluate check results and client attributes after the final check. The **first matching rule** sets the rule-based outcome. If no rule matches, the default result applies.

**Compliance policies** are evaluated after outcome rules and can still raise **Attention**. When a rule determines the outcome, the session displays **Set by outcome rule** with the rule's name.

A team member's **direct session outcome override** takes precedence over automated outcomes. Changing an individual check's result can cause rules to be evaluated again, but does not overwrite a direct manual session override.

Outcome rules set the **session outcome**; individual **check results** remain available for review. See Outcome rules and actions for configuration and evaluation details.

### Policy assurance <a href="#toc_10" id="toc_10"></a>

For workflows with attached Compliance Policies, review evaluation results under **Policy Assurance**. These show how the verification evidence was assessed against the assigned regulatory, industry, or internal requirements.

<figure><img src="https://1615271746-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKyFKMqftsmT6qln9zo5y%2Fuploads%2Fp7As2QQXnDG0MPH4HlM7%2Fworkflows_policy_assurance_v2.png?alt=media&amp;token=87320860-f634-4fa2-8fb2-e2d6efb09808" alt=""><figcaption><p>Workflow Session - Policy assurance</p></figcaption></figure>

Not every workflow includes policies. Review the workflow configuration and attached policy revisions when investigating a policy result.

### Accessing results and notifications <a href="#toc_11" id="toc_11"></a>

<table><thead><tr><th width="151.39453125">Method</th><th>Use it to</th></tr></thead><tbody><tr><td><strong>Portal</strong></td><td>Review progress, check outcomes, policy results, and supporting evidence.</td></tr><tr><td><strong>API</strong></td><td>Retrieve workflow session information for your application or downstream processes.</td></tr><tr><td><strong>Webhooks</strong></td><td>Receive notifications when sessions complete or their outcomes are updated.</td></tr><tr><td><strong>Reports</strong></td><td>Export data for operational analysis, audits, and recordkeeping.</td></tr></tbody></table>

Use the Workflow Sessions API to retrieve session information. See the Webhooks API Reference for supported session events and the Webhooks Guide for integration guidance.

### Monitoring performance <a href="#toc_12" id="toc_12"></a>

Workflow analytics help you understand where customers complete verification, leave the journey, or encounter failures.

<figure><img src="https://1615271746-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKyFKMqftsmT6qln9zo5y%2Fuploads%2FyZEzz0emvzfh8qtFkp8J%2Fworkflow_performance.png?alt=media&amp;token=95baca1a-eea4-4b14-ab0d-c3c9e4b8d82d" alt=""><figcaption><p>Workflow stats and performance</p></figcaption></figure>

Review **completion rates**, **abandonment rates**, **failure rates**, and **average verification time** for each workflow. These metrics allow you to:

* Refine workflows to reduce friction.
* Optimize check configurations to better match your target demographics.
* Add or remove checks as risks evolve.
* Improve decisioning speed.
* Enhance customer experience.

Keep verification requirements aligned with your customer population and risk process when adding, removing, or changing steps.

### Frequently asked questions <a href="#toc_13" id="toc_13"></a>

<details>

<summary>What is the difference between a workflow and a workflow session?</summary>

A **workflow** defines the checks, settings, policies, and actions used for verification. A **session** records one customer's journey through a version of that workflow.

</details>

<details>

<summary>Can a Complete session still require manual review?</summary>

Yes.

**Complete** is a session state, while **Attention** is an outcome. A session can finish processing and still contain findings that need a reviewer.

</details>

<details>

<summary>Can customers resume an incomplete session?</summary>

Yes, while its state is **Started**. If it becomes **Abandoned** or **Cancelled**, start a new session for the customer.

</details>

<details>

<summary>Do workflow updates change sessions already in progress?</summary>

No.

Existing sessions retain the workflow version they started with.

</details>

<details>

<summary>Where can I see why a session received its outcome?</summary>

Review **check results**, **policy assurance**, and the **activity timeline**. If an outcome rule determined the result, the session shows **Set by outcome rule** and the rule's name.

</details>

<details>

<summary>Can my application receive workflow results automatically?</summary>

Yes.

Subscribe to the relevant **workflow session webhook events** and use the **Workflow Sessions API** to retrieve the session information your application needs.

</details>

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.complycube.com/documentation/product-guides/compliance-studio/workflows/workflow-sessions-and-results.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
