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

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Build workflows

ft:clusterId :

    - crworkflow

bundleId :

    - crworkflow

workflow :

    - Creator


---

# Wait for condition workflow activity

# Wait for condition workflow activity {#ariaid-title1}

Release version: Yokohama  
Updated January 30, 2025  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Wait for condition workflow activity

The Wait for condition workflow activity in ServiceNow pauses the workflow at a specific step until the current record meets a defined condition.
It continuously evaluates the record each time it is updated and resumes the workflow only when all specified conditions are true.
This activity is ideal for waiting on external events such as record updates, but not for changes made within the same workflow.
For time-based pauses, the Timer workflow activities should be used instead.
Show full answer Show less  

## Key Features

* **Condition-Based Waiting:** The workflow pauses until the condition or condition script evaluates to true based on the current record.
* **Timeout Option:** You can enable a timeout to limit how long the workflow waits, preventing indefinite pauses. A duration and optional schedule can be set to control when the workflow proceeds if the condition is unmet.
* **Result Handling:** The workflow designer can assign a result value programmatically, which determines when the activity transitions.
* **User Context:** Condition activities run as the user whose actions meet the condition, ensuring proper context in the workflow execution.

## Input Variables

The activity behavior is controlled by several input fields:

* **Condition:** The criteria that must be met for the workflow to continue.
* **Condition script:** A script that sets an answer variable to true to satisfy the wait condition.
* **Enable Timeout:** When enabled, specifies that the workflow will stop waiting after a set duration if the condition is not met.
* **Duration:** The amount of time to wait before timing out, entered in hours, minutes, and seconds.
* **Schedule:** Optional schedule to calculate the timeout period based on work hours.

## Activity States

The workflow engine manages the Wait for condition activity through these states:

* **Executing:** The activity starts running.
* **Waiting:** The activity pauses until the condition is met or an event triggers continuation.
* **Finished:** The activity completed execution, with the result indicating success or failure.
* **Cancelled:** The activity or the entire workflow was canceled.
* **Error:** A JavaScript error occurred; logs should be reviewed for details.

## Practical Considerations for ServiceNow Customers

Use the Wait for condition activity to efficiently pause workflows awaiting external record updates without consuming unnecessary resources. Configure timeouts to avoid indefinite waits and ensure workflows progress smoothly. Avoid waiting on workflow-internal field changes directly---use timers instead to detect such changes reliably. Understanding and leveraging these settings helps maintain responsive and accurate workflow automation in your ServiceNow environment.  
The Wait for condition activity causes the workflow to wait at this activity until the current record matches the specified condition. {#r_WaitForCondition__wf-wait-for-activity-shortdesc}
The workflow evaluates the Wait for condition activity each time the
current record is updated. Use this activity to pause a workflow indefinitely until a
particular criteria is met by a record update. To pause a workflow for a timed duration see
[Timer workflow
activities](https://www.servicenow.com/docs/access?context=c_TimerActivities&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US).  
For workflow to consider the condition met, all conditions specified -- whether in the builder or in a script -- must be true.  
Note:  
A Wait for condition activity should only be used to wait for an external event such as a record update, and not one from a workflow setting a value. If you have a workflow setting a value and want to wait for that same field to be seen as 'changed,' try inserting a one-second timer.

## Results

The workflow designer can assign a result value using `activity.result` from
within a script field of the activity. The activity transitions when the result value is
true.

## Input variables

The following variables determine the behavior of the activity.  
Note:  
Condition activities run as the user whose actions match the conditions the workflow was waiting for and advances the workflow.
{#r_WaitForCondition__table_uml_1qt_jp__entry__2}

| Field | Description |
|-|-|
| Condition | The workflow is paused at this activity until this condition matches the current record. |
| Condition script | If specified, the workflow is paused at this activity until this script sets the <var class="keyword varname">answer</var> variable to true. |
| Enable Timeout | Option to limit the amount of time that the workflow waits for the activity to be completed before continuing. Note: Use the Enable timeout option to prevent this activity from continuing to run. If the condition to continue is never met, a timeout value specifies when the system skips the Wait for Condition activity and goes to the next item in the workflow. You must set a Duration value to enable a timeout. You can also select a Schedule if you want to compute the duration end date based on a specific work schedule. |
| Duration | Amount of time that the workflow waits before continuing when the Enable timeout option is selected. Enter the time to wait in hours, minutes, and seconds. If you leave this field empty, the workflow does not wait. |
[Table 1. Wait for condition activity input variables]

{#r_WaitForCondition__table_uml_1qt_jp}

## States

The activity state tells the workflow engine what to do with the activity.{#r_WaitForCondition__table_wvy_pqt_jp__entry__2}

| State | Description |
|-|-|
| Executing | The workflow engine knows to start the onExecute function of the activity. |
| Waiting | The workflow engine ignores the activity until a specific event to restart the activity is fired. |
| Finished | The activity finished running. See the result value for the outcome of the activity. |
| Cancelled | This activity, or the workflow that contains this activty, was canceled. |
| Error | A JavaScript error occurred. Review the logs for error details. |
[Table 2. Wait for condition activity states]

{#r_WaitForCondition__table_wvy_pqt_jp}