'Ask for Approval' action is returning "Skipped" as Run time value in Flow designer

Nivetha K
Kilo Contributor

Hi All,

I'm trying to configure a flow designer for a record producer whose target table is also a custom one.

Table Name: u_fwrule_task

After submitting the SR, a task record will be created in FWRule Task table. I need to have a group approval after the record gets created in FWRule task table. But, my flow is skipping the approval and marking the flow as 'Completed' without moving to next action.

Attached flow, flow execution details and 'Ask for approval' action screenshots.

Can anyone please guide me on how to make my request proceed further using flow designer?

1 ACCEPTED SOLUTION

BhupeshG
Tera Guru

Make sure, your group is accessible via the correct domain.

 

In the domain separated instance, it is important to test the flow also in respective domain so that it can access the data it needs

View solution in original post

15 REPLIES 15

Hello Ankur,

Yes, I implemented Dirk's response in my instance, even then it is not working.

Below is the relationship created between my custom table and sysapproval_approver table, still flow is not proceeding further and returning the runtime value as 'Skipped'.

find_real_file.png

Not very sure then

I believe in his comment he mentioned to insert record into sysapproval_approver table

Regards,
Ankur
Certified Technical Architect  ||  9x ServiceNow MVP  ||  ServiceNow Community Leader

Hi,

check point mentioned by Dirk in this link

User Approval for a Non Task Custom Table.

Regards
Ankur

Regards,
Ankur
Certified Technical Architect  ||  9x ServiceNow MVP  ||  ServiceNow Community Leader

BhupeshG
Tera Guru

Make sure, your group is accessible via the correct domain.

 

In the domain separated instance, it is important to test the flow also in respective domain so that it can access the data it needs

Hi Bhupesh,

Yes, corrected my domain for both group and flow. It is finally working as expected now.

Thank you so much for your guidance, Bhupesh 🙂

 

 

Regards,

Nivetha K.