Delay Until Issue

(0) Share

Report

Posted on by Andrew_J

1,962 Moderator

Hi All,

I have flow that is working perfectly when I run it in test however when I start using it the real world, i.e. with third parties outside my organization this is where I run into issues. Some people external to us need to sign an agreement, I have therefore built a delay unit step for this purpose. But this delay until is only running for about 1d:10m before it then sends a copy of the unsigned agreement to the clients payment processing team. The part of the flow is as follows:

In delay until step I have the following:

I think this is a time out is the issue, I am wondering what I should put in here as I think I need to give the signatories at least two weeks to sign but I am sending daily reminders as part of the flow, so they should get the message well before that.

So I hope someone can help.

Regards

Andrew

Categories:

Building flows

I have the same question (0)

All responses (4)

Answers (1)

grantjenkins 11,063 Moderator on at

Like (0)

Report

Re: Delay Until Issue

You might need to check the Do Until limits.

----------------------------------------------------------------------
If I've answered your question, please mark the post as Solved.
If you like my response, please consider giving it a Thumbs Up.

Was this reply helpful? Yes No
Andrew_J 1,962 Moderator on at

Like (0)

Report

Re: Delay Until Issue

Hi @grantjenkins,

I have been and done some research about the above but it seems to be as clear as mud.

I know the count and the time out are not want I want. I think I still want a long timeout, so the P30D maybe okay. However I am sending reminder every 24 hours for the person to sign the document. However the count is the issue. I am not sure what to put in there and I am wondering by putting the delay time function in the location I have maybe causing an issue.

I think from what I have read that the delay time has a relationship to the count, so if I change the delay time to 6 hours and count of 100, this in my mind would be 6hrsx100x60min=36,000mins with a day of 1440min this would mean that the count would run for 25 days. Should I move the delay time operation to the top.

This 25 days would take account for leave and hopefully after 25 reminders the person would realize they have something to do.

I am on the right path or have I completely misunderstood this.

Regards,

Andrew

Was this reply helpful? Yes No
Verified answer

grantjenkins 11,063 Moderator on at

Like (0)

Report

Re: Delay Until Issue

6 hourly = 4 times per day
4 times per day x 30 days = 120 iterations

So, you could set your count to 120 and it would coincide with your delay, etc. And keep timeout to P30D.

I would put your Delay action just above the Get the status of an agreement. That way it won't end up delaying for another 6 hours after it's found that the agreement has been signed.

Was this reply helpful? Yes No
Andrew_J 1,962 Moderator on at

Like (1)

Report

Re: Delay Until Issue

@grantjenkins

Thanks for the explanation of the math, that was what I was not getting and what know one else, elsewhere was explaining to.

I will make this as solved, but I still have to test this anger. I have decide to set the delay at 2h c=360 and to=30d, as I thought a delay of six hours was too long as it could mean a difference between one payment day and another week.

Regards,

Andrew

Was this reply helpful? Yes No