Reminder Email after 3 Days if Approval Is Still Pending – Flow Designer Implementation Help

ItayB
Tera Contributor

Hi everyone,

I'm working on a catalog item flow ("New Hire") that includes two approval steps. I need to implement a reminder notification if the first approver does not respond within 3 days.

Here's what I'm trying to achieve:

  • After sending the first approval, wait up to 3 days.

  • If the approval is still in "requested" state after 3 days (i.e., no action taken), send an email reminder to the approver.

  • If the approval is completed earlier, the flow should continue without waiting the full 3 days or sending a reminder.

What I’ve done so far:

  • Used a Wait for Condition with a 72h timeout.

  • Then added a Lookup Record on sysapproval_approver to retrieve the relevant approval record using document_id, approver, and state = requested.

  • Followed by an If condition and Send Notification action.

My challenge:

In Flow Designer, I had difficulty finding the document_id field in the sysapproval_approver table. I had to type it manually.

Is this the recommended approach?
Would you suggest a better way to reliably identify the pending approval and check its state after timeout?

I add some photos of my Flow (I deleted what i did here to start a "clean" solution)

 

ItayB_0-1752405546841.pngItayB_1-1752405573241.png

 

Thanks in advance!

 

Itay.

1 ACCEPTED SOLUTION

ItayB
Tera Contributor

Finally I realized that I could use another FLOW,
I executed it on the authorization table and now everything works.
Thank you very much everyone for the help and effort.

View solution in original post

12 REPLIES 12

ItayB
Tera Contributor

The Solution must be from the first Flow .. 

kalpanashar
Tera Contributor

The document_id field in the sysapproval_approver table is a Document ID type, which references records across multiple tables. Because of its dynamic nature, it doesn’t always show up in Flow Designer’s field picker. That’s why you had to manually type it and yes, that’s currently the recommended workaround.

ItayB
Tera Contributor

Finally I realized that I could use another FLOW,
I executed it on the authorization table and now everything works.
Thank you very much everyone for the help and effort.