---
sourceDocument: Australia Build workflows
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/build-workflows

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Build workflows

ft:clusterId :

    - crworkflow

bundleId :

    - crworkflow

workflow :

    - Creator


---

# Playbook activity state mapping

# Playbook activity state mapping {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Use playbook activity state mapping to override the status of a playbook
card.
A playbook card's state comes from the Activity State by default. Activity states come from
the Sub Flow or Flow Action powering the activity.  
Activity Definition authors can specify a records to provide the status shown in playbook cards. This record is referred to as an Experience Status Record. It is specified within an Activity Definition's experience properties.  

Any record from any table can be used as an Experience Status Record. Default activity
definitions use sys_flow_data records as their Experience Status
Record.
Figure 1. Activity States displayed in card view

## Default Activity States {#playbook-activity-state-mapping__section_u31_fpz_lnb}

{#playbook-activity-state-mapping__table_ew3_kqz_lnb__entry__2}

| Status | Flow State |
|-|-|
| Pending | Flow has not started |
| Ready | Flow is |
| In Progress | Flow is running |
| Complete | Flow has finished |
| Skipped | Flow was skipped due to conditions |
| Error | Flow encountered an error |
| Canceled | Flow was canceled |
[Table 1. Out-of-the-box Default Activity States in sys_flow_data record]

{#playbook-activity-state-mapping__table_ew3_kqz_lnb}  
Activity states are used in the following:

* Declarative Action conditions
* Activity Override conditions
* Animations
* Card visual experience
{#playbook-activity-state-mapping__ul_mvj_ssf_mnb}

## Exceptions {#playbook-activity-state-mapping__section_jrk_yrz_lnb}

Business logic doesn't always align one-to-one with the flow. The following are examples of exceptions:

* An agent clicks Skip on an instructional card. The flow displays as complete, but the business logic is skipped.
* A flow may never complete if a task is waiting for input from an agent to restart a loop. The associated task is effectively complete in this state.
{#playbook-activity-state-mapping__ul_g3x_csz_lnb}
* **[Playbook activity state-mapping rules](https://servicenow-prod.fluidtopics.net/BWglKgKY9bxEBwJ99IAnFA)**   
  Map playbook activity states to states from the given experience record.
* **[Playbook activity state-mapping permissions](https://servicenow-prod.fluidtopics.net/o~TWfboodfVIrU9h9RJi_g)**   
  User permissions must be assigned to allow agents to complete or skip activities in playbook using activity state mapping.