---
title: "Step and process timers"
slug: "step-and-process-timers"
updated: 2025-05-28T18:40:40Z
published: 2025-05-28T18:40:40Z
canonical: "support.tulip.co/step-and-process-timers"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.tulip.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Step and process timers

## Overview

In Tulip, you can create two types of timers within an individual app:

1. Timers that count up from 0:00
2. Timers that count down from a predetermined number

These timers can track time at two levels:

1. Time spent on an individual Step
2. Time spent in the entire app

Here's how to create these timers. Both timers only reset when an app is "Completed" or "Cancelled". The amount of time spent in the app is also automatically stored when an app is completed or cancelled. Read more about the [app completion concept](https://support.tulip.co/docs/how-to-complete-an-app) here.

## Create a timer that counts up

In order to add a step or process timer that counts up (or increases):

1. Go to the Step within the app where you would like to add a timer (or go to the Base Layout)
2. Select the **Text** option on the Tool Bar.
3. Select **Variable**

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/How%20to%20Add%20Step%20and%20Process%20Timers_92385951.png)

1. In the Side Pane, select **App Info** as the **Datasource**
2. Select **Time Elapsed on App**, or **Time Elapsed on Current Step**, as the **App Info**

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/How%20to%20Add%20Step%20and%20Process%20Timers_299943199.png)

This timer will automatically begin counting as soon as an operator opens the app or step in the Tulip Player.

## Create a timer that counts down

The **Step Time (or Step Cycle Time)** refers to the time that an operator should take to complete all activities in the step and move to a new Step.

Similarly, the **Process Time or (Process Cycle Time)** refers to the time that an operator should take to complete all activities in the app being run.

## Edit Step and Process Timers

### Step Cycle Time

1. Click on the **step** for which you would like to update the Step time.
2. In the Step Tab, click into **Step Cycle Time** in the Side Pane.

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/How%20to%20Edit%20Step%20and%20Process%20Timers_71158907.png)

1. Edit the time.
2. Click the **green check mark** to confirm your input.

### Process Cycle Time

The **Process Cycle Time** is set as the sum of the Step Cycle Times, however, it can be edited the same way as the Step Cycle Time. There is one exception though, Process Cycle Time is a feature of the process and not the Step and hence will be found under the “Process” tab.

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/How%20to%20Edit%20Step%20and%20Process%20Timers_71158908.png)

### Step timer widget

1. Click on the **step** for which you would like to add a step timer.
2. Click **Embed**, and select **Step Timer**

The following Side Pane will open:

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/How%20to%20Add%20Step%20and%20Process%20Timers_299944185.png)

- **Title**: Name your timer
- **Time Duration:** Select either your *Step Cycle Time* or *App Cycle Time*
- **Target Time**: Set the target time of the timer. To statically set the timer, select *Static* *Value* or *App Info*. To dynamically set the timer select *Tulip Table Record*, or *Variable*.
- **Warning At / Overtime At:** Set warnings for your timer

### Set Target Cycle Time

To set the Target Cycle Time for an individual step, click on the step, and select the Step Tab from the Side Pane. Next, edit you Step Cycle Time

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/How%20to%20Add%20Step%20and%20Process%20Timers_299945455.png)

To set the Target Cycle Time for an entire app, select the **App** tab from the side pane.

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/How%20to%20Add%20Step%20and%20Process%20Timers_299945834.png)

Your App's Target Cycle Time, or you Process Cycle Time can be set to be a custom length, or the sum of your step's times.

## Use Timing Values In Triggers

You can store the amount of time spent on a specific step or on the entire app in a Variable or Table Record.

Here's an example of a "Then" statement that stores the amount of time spent on a step when an operator presses a button:

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/How%20to%20Add%20Step%20and%20Process%20Timers_153194860.png)

- "Data Manipulation" --> "Store" --> "App Info" --> "Time Elapsed on Current Step" location: "Variable"

## Further Reading

- [How To Use the Expression Editor in the App Editor](https://support.tulip.co/docs/how-to-use-the-expression-editor-in-the-app-editor)
- [A List of Actions in the Trigger Editor](https://support.tulip.co/docs/list-of-actions-and-transitions-in-the-trigger-editor)

---

Did you find what you were looking for?

You can also head to [community.tulip.co](https://community.tulip.co/?utm_source=intercom&utm_medium=article-link&utm_campaign=all) to post your question or see if others have faced a similar question!

**Step**

A view your users will see within an application. **Steps** can be viewed chronologically or in whatever order best fits your process.

Steps can be grouped into **Step Groups**to manage and organize your app Steps.

**App Completion**

**App Completions**are a mechanism to store immutable data from a Tulip app. When an app is completed, all **Variable's**current values will be stored in the app completions tab.****This completion data can be analyzed in **Analytics.**

By default, after a Completion users will be brought back to the **Begin Screen**of your application. This behavior can be adjusted with other **Transition**types.

**App Cancel**

**App Cancels**are a restart of an application without storing its data in a **Table.**

By default, after a cancellation users will be brought back to the **Begin Screen**of your application. This behavior can be adjusted with other **Transition**types.

**Variable**

**Variables**are a location to store app information. Variables have a specific type that must match the contents they can store.

Variables are only accessible within a single application and are cleared when the app is restarted or completed.

**Side Pane** **(Context Pane)**

The**Side Pane**is the configuration pane on the right side of the **App Editor**where steps, apps, and widgets can be configured. **Triggers**can be added to adjust widget behavior.![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Context%20Pane.png)

**App Info**

**App Info**is a subset of the data available within an application automatically. This data can be used both in **Widgets**and**Triggers.**This includes the current date and time, the app name, the app version, the current shift, and more.

**Tulip Player**

**Tulip Player** is the Windows/Mac executable program where users can run Tulip apps. Tulip player allows you to create a more seamless user experience by removing the need for a web browser and allows increased IT controls.

**Step Tab**

In the **Side Pane**, the**Step Tab**is where you can adjust all of the **Step-level**settings, including **Step Triggers,**Step background, Step resolution, and more.![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Step%20Tab.png)

**Trigger**

**Triggers** are groups of logic that are tied to an app event, such as step open, timer, widget interaction, etc. App builders can add triggers to **widgets**, **machines**, **devices**, **apps**, and **steps**.

**Triggers** can contain **actions**, **transitions**, and **conditions**.

**Table Record**

A **Table Record** is a reference to a row in a **Tulip Table**. Table Records can be created either from the Table UI or from with an App Trigger.

To edit a record it must be loaded into a **Table Record Placeholder.**