# Workflow wait condition not working

**URL:** <https://community.glideapps.com/t/workflow-wait-condition-not-working/80160>\
**Category:** Ask for Help\
**Tags:** workflows\
**Created:** [February 19, 2025, 6:37am UTC](https://community.glideapps.com/t/workflow-wait-condition-not-working/80160 "2025-02-19T06:37:31Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![blairrorani](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/blairrorani/32/43426_2.png) [@blairrorani](https://community.glideapps.com/u/blairrorani)\
**Post date:** [February 19, 2025, 6:37am UTC](https://community.glideapps.com/t/workflow-wait-condition-not-working/80160/1 "2025-02-19T06:37:31Z")

</div>

I have a wait condition that waits for a field to be _not empty_.  
It’s the second one down in both branches.

 ![Screenshot 2025-02-19 at 17.35.42](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/1/d/1de43166ecaec6e81b936291a84da9f4140068bc.png)

However, the condition isn’t met and the field in the condition is still empty right now. The workflow still completes subsequent steps.  
For example, you can see the column on the right is populated with is the **Set column values** step in the workflow.

 ![Screenshot 2025-02-19 at 17.35.25](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/5/4/546ef156d4f4d2b4b8cce6ca1431b7609715734b.png)

Should the workflow stop and return an error message that I configured rather than continuing?

---

<div class="post-metadata">

**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [February 19, 2025, 7:37am UTC](https://community.glideapps.com/t/workflow-wait-condition-not-working/80160/2 "2025-02-19T07:37:58Z")

</div>

> [@blairrorani](#):
>
> Should the workflow stop and return an error message that I configured rather than continuing?

That’s what I would expect, yes.

I assume that you are writing the response from the first step into this column?  
What do you see as the output of the first step if you examine the run log?

Side note: would you ever expect more than one user to trigger this action? If yes, that api\_respone column should be user specific, otherwise you may have users bumping into each other.

---

<div class="post-metadata">

**Author:** ![blairrorani](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/blairrorani/32/43426_2.png) [@blairrorani](https://community.glideapps.com/u/blairrorani)\
**Post date:** [February 19, 2025, 7:47am UTC](https://community.glideapps.com/t/workflow-wait-condition-not-working/80160/3 "2025-02-19T07:47:34Z")

</div>

![Screenshot 2025-02-19 at 18.43.43](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/7/4/7401657db7b936e9aa3e250a07f695fd70e78b1f.png)

Mostly one person uses this tool at a time, but there could be two. However, the run time is so short chances of bumping into each other is low. The data is for a given row and only one person would work on a row at a time as it’s a workflow you complete yourself (generating leads, adding to CRM and contacting them).

The reason I say this isn’t working is because I can see the subsequent steps were completed, that’s what my second screenshot shows, the far right column is only populated after the wait condition is met. Which is wasn’t in a couple of cases.

I decided to change the condition to if there api response is 201 after 3 seconds then continue.

---

<div class="post-metadata">

**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [February 19, 2025, 8:39am UTC](https://community.glideapps.com/t/workflow-wait-condition-not-working/80160/4 "2025-02-19T08:39:57Z")

</div>

You need to expand those run history logs so you can see the output from the individual steps. I’m just curious to see if your API call is actually returning anything.

---

<div class="post-metadata">

**Author:** ![blairrorani](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/blairrorani/32/43426_2.png) [@blairrorani](https://community.glideapps.com/u/blairrorani)\
**Post date:** [February 19, 2025, 9:01am UTC](https://community.glideapps.com/t/workflow-wait-condition-not-working/80160/5 "2025-02-19T09:01:53Z")

</div>

oh sure:

It isn’t returning anything which is what alerted me in the first place.  
The logs don’t show what the API returns, I store the response in a column but column is empty. You can see in original post the response column is empty.

 ![Screenshot 2025-02-19 at 20.00.33](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/9/5/958b77f4e2a395e470e10d78916a3a6019adb682.png)

This is the error message that I assume would stop the workflow.

---

<div class="post-metadata">

**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\
**Post date:** [February 20, 2025, 12:40am UTC](https://community.glideapps.com/t/workflow-wait-condition-not-working/80160/6 "2025-02-20T00:40:25Z")

</div>

So the “for add\_org/api\_response” step is waiting for api\_response to be not empty, but your Pipedrive API call didn’t return anything?

Is that column interacted with by any other actions?

---

<div class="post-metadata">

**Author:** ![blairrorani](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/blairrorani/32/43426_2.png) [@blairrorani](https://community.glideapps.com/u/blairrorani)\
**Post date:** [February 20, 2025, 5:07am UTC](https://community.glideapps.com/t/workflow-wait-condition-not-working/80160/7 "2025-02-20T05:07:23Z")

</div>

Yes, I changed it to be the api response code column that waits for the value to be 201 (added), see how that goes.

But yeah, Glide basically blew past that false condition and completed workflow in a couple of cases.
