I have a wait condition that waits for a field to be not empty.
It’s the second one down in both branches.
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.
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.
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.
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.
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.
This is the error message that I assume would stop the workflow.
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?
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.
