Dear ServiceNow, you need to do better and solve this (introducing manual wait periods in flows)

[Jacob Saaby Nie]

This is related to flows, so I'm not sure if this is the right place.

In any case, I have a HI case related to this: https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1274727

(And just to be sure, this is not blaming the HI support, this is aimed at your developers)

In that KB it says to introduce a waiting period after e.g. a look up. Because if you use e.g. the result of a lookup immediately after in another action, that action might error out saying "Value of field record is not a GlideRecord".

So, introduce e.g. a 30 second timeout between the two.

I'm sorry ServiceNow, I thought we were out of the 90's by now!?

You formally advise a max of 50 actions in a flow. And one of those actions, you want us to spend waiting?

Would it not be prudent if you designed your Flow engine/actions, so we can always trust that if there's a result from something, we don't have to introduce junk like this in our flows?

In this case, the process is that someone enters a CI record in a field and saves it. The next action does something based on that.

When someone enters data and saves, are you REALLY telling me that the platform isn't... ready... yet?

This is amateur stuff ServiceNow. Do better! At this pricepoint we VERY much expect you to! This is just plain embarassing.