What is alternative of For Each in flow designer ?

[Ct111]

Hello community members,

What is alternative of For Each in flow designer?

Currently , i have a flow in which For Each is running on Lookup records but it is throwing error without any log records.

I also went through an article which suggest running as system users but my flow is already running by system user and it still throws error.

Does anyone have alternative or substitute for this For Each?

[Hayo Lubbers]

Hi @Ct111 ,

If you don't have log records, enable (temporary) the logging options in the system. Probably setting the system property "com.glide.hub.flow_engine.log_level" to DEBUG is sufficient, but more options and (log) settings can be found here: https://docs.servicenow.com/bundle/washingtondc-build-workflows/page/administer/flow-designer/refere...

More information about error handling in a flow: https://docs.servicenow.com/bundle/washingtondc-build-workflows/page/administer/flow-designer/concep...

It's not an alternative, but rebuilding the step(s) in e.g. a subflow doesn't solve your problem. The first step is to identify the issue, then you can look for a solution/workaround.

Regards,

Hayo

[AnirudhKumar]

When you say 'its throwing error', what do you mean?

[Mani A]

What is the error? If your using lookup step on table and then for each to check the data from table ..sometimes it Will throw error and it depends on table data ( if it has large number of records) ..so better to use wait for condition/some delay before for each step...