All topics
Get started8Account, team & permissions44Units & fields70Records, views & tasks39WhatsApp & Cortex Chat68Email & social27Lead ads & distribution38Automations52Documents & quotes32Dashboards40Cortex AI18Developers & API12
Help Center·448 guidesAll topicsContact support

Start an automation when a field stays the same for a while

The trigger A field stays the same for a while catches stuck records, such as “the status stayed New for 24 hours”. It counts real time or business hours only.

7 min
Before you start · for owners and managers
Permission to edit workflows
  • You need: Permission to edit workflows

Steps

1
Choose the trigger A field stays the same for a while and the unit.
2
Under Which field, and which values?, choose a field with options: a dropdown, a status, a priority, a multiple choice, a tag, or a source.
Text and number fields aren’t available here.
3
Choose one or more values. It’s enough for the record to have one of them.
4
Under For how long?, set the time in minutes, hours, days or weeks.
5
Under Count time using, choose which clock counts.
Every hour, day and night, Working hours you set, or The record owner’s working hours.
6
Add the actions, then check how many records are due right away before you turn it on.

How is time counted?

Clock
What it means
Every hour, day and night
Every hour counts, night and day
Working hours
Days and hours you choose, in the workspace’s time zone
The record owner’s working hours
The owner’s Working Hours, set on their member in Settings → Members; if none are set, every hour counts

A day of business hours equals 24 counted hours. “3 days” on a 09:00–17:00 schedule means 9 working days. That’s why it shows “3 days of business hours” and not “3 working days”.

Night shifts are allowed: 22:00–06:00 belongs to the day it starts on.

When does the count start again?

Any change to the field resets the count to zero, even if a bulk edit or another automation made it. Moving between two chosen values resets the count too.

Writing the same value again with a bulk edit doesn’t reset the count.

A record that left the value and then came back to it is counted again, and can trigger the automation again.

Before you turn it on: due right away

When you turn it on, Corteksa works out when each record entered its value, from the change history or from its creation date. Records that have already passed the time start right away, and you see how many before you turn it on.

Coming up

Under Coming up, the automation shows a list of the records that are waiting, sorted by when they’re due, with a progress bar for each record. You only see records you’re allowed to see.

Special variables

{{stuck_since}} is how long it’s been in the value, {{time_in_value}} is the actual time, {{field_label}} is the field’s name, and {{value_label}} is the value it stayed on.

If something goes wrong

What you see
Why
What to do
“The field has no set values”
You chose a field that doesn’t have options.
Choose a status or dropdown field.
“The value doesn’t exist”
An option was deleted from the field after you chose it.
Choose the values again.
“The start and the end can’t be the same time.”
Business hours start and end at the same time.
Change the end time.
“Skipped — the value changed before the run started.”
The field changed at the last moment.
This is normal; the record isn’t stuck anymore.
I moved a record to another unit and it wasn’t counted
The count is tied to the original unit.

A real example

Namaa Academy
The situation

Salespeople forget the clients who stay at “New”.

What they did
  1. The field: Stage. The value: “New”. The time: 8 hours of the record owner’s working hours.
  2. A notification to the assignee’s phone.
  3. A follow-up task due today.
The result

The salesperson is alerted only after a full working day, and not over the weekend.

A made-up company, to show the idea. The numbers are rounded.

Good to know

The time is from 5 minutes to 90 days of counted time.
Up to 50 values in the trigger.
The start may be up to about 3 minutes late.
It runs once per stay. Pausing and turning it on again doesn’t repeat it for the same stay.
The count of records due right away stops at 5,000 and shows “5000+”.
It doesn’t support including existing records; records that are due start on their own.
Did this guide solve it?
If not, we’ll ask what was missing.
Open in Corteksa
Did this guide solve it?

We read every answer. To get a reply, use Contact support.