Rescheduling AbsoluteTimeAutoAdvancer in Workflow is not working.

[pavankumarn993]

Hi All,

Facing issue while rescheduling AbsoluteTimeAutoAdvancer in workflow.

I created a custom workflow to schedule a press release email. For this I am adding "absoluteTime" metaData in workflow process step followed by AbsoluteTimeAutoAdvancer in participant step.It is scheduling as expected in this scenario.

But when I tried to reschedule same workflow instance by postponing the date, it is still getting executed for older time even after changing "absoluteTime" metaData to newer timestamp.

Is it possible to reschedule the workflow using AbsoluteTimeAutoAdvancer?

Please let me know if I am missing out anything.

Thanks in advance.

[smacdonald2008]

Are you looking to invoke a workflow based on time intervals?

[pavankumarn993]

I am using time out handler in participant step

Selected timeout as :Immediate and

handler : AbsoluteTimeAutoAdvancer

Which internally uses "absoluteTime" metadata of workflow. Once time is reached it advances to next step in workflow.

Here I am trying to reschedule time which is not working out.

[smacdonald2008]

See of this older thread helps -- Participant Step does not Timeout and Auto Advance

[pavankumarn993]

I followed this article already. In my case it is working for the first time when time out happens.

But if I change time before timeout , still it is advancing to next step for the old time. I want to understand possibility of changing time , will it works ?

[smacdonald2008]

It works the first time. Does the same workflow work a second time if you do not modify the time?

[pavankumarn993]

Yes it works for the second time if I do not modify time.

If I change time to 'time b' which is future time than already scheduled time 'time a', workflow is advancing to next step at old time i.e at 'time a'  not at 'time b'.

[pavankumarn993]

Any one facing the same problem, please let me know.

[smacdonald2008]

This is not a configurable setting that can be fixed or a community member can address. If you are experiencing this - it could be a bug. Please open a support ticket so this can be fixed.