Question

Forms In flight submissions - Timer Event trigger on server restart

Forms

Updated October 9, 2021

asked on October 6, 2021

Hello, We are running 10.4.4 Laserfiche forms. We recently ran into an issue where submissions that are currently in flight (submitted and in progress) had their timer events triggered off email occur due to a server reboot. All the inflight items that were past the due date of the timer triggered off as a result of the server restarting. The inflight items never executed the timer events previously because the timer events were added into the process at a later time. The system basically saw that they were past the timer due date and executed anyways, vs ignoring them because they were added into the process after the fact.

Has anyone ever ran into this, is this intentional system design or a bug?

0 0

Answer

SELECTED ANSWER

replied on October 9, 2021 • Show version history

The behavior is intentional system design, when restart the server(actually restart Laserfiche Forms Routing Service), there is a timer registration process since previous registered timers stored in memory are wiped out due to server reboot. When calculate which timers need to be registered, it will check whether the attached tasks are still in progress. No matter the timer event is added before or after the user task is started, it will always be registered as long as the user task is still in progress. If the time configured for the timer event is in the past, the timer event will be triggered immediately. The use case for this behavior is a timer event is attached to a user task to wait for 2 days, but after the user task is started for 1 days, the Laserfiche Forms Routing Service is stopped for 2 days unexpectedly, when start the Laserfiche Forms Routing Service at day 3, the timer attach the the user task will be registered and will be triggered immediately.

0 0

Replies

replied on October 8, 2021

Can you provide more details for the issue you ran into?

1. The screenshot of the timer event options from process diagram

2. The screenshot of the instance history to show when did the timer event is triggered.

0 0

replied on October 8, 2021

Here are some examples (2): Both firing off timer catch events 1, 2 because they are past the 21 day, and 35 day marks. Both of these were in flight sitting because they past the timer marks. When the server rebooted, it looked at the days sitting and triggered the 21 and 35 day timers. (i have about 100 submissions that were fired off being in flight before the timers were added, then server restart and they fired off)

They all occur at the server reboot time @ 10/3 ~ 8:04PM

Design - step with timers:

Simple timer to wait 21 days (does not repeat)

0 0

You are not allowed to follow up in this post.

Question

Question

Forms In flight submissions - Timer Event trigger on server restart

Answer

Replies

Sign in to reply to this post.