Form session expired (Session-Timeout)

Modified on Thu, 26 Sep at 2:33 PM

The form session expires after 30 minutes in the standard configuration. The Oops-error-message will then appear when the form is submitted. There is no entry in the process-protocol because the error does not occur during workflow processing:

Oops-error-message when sending with expired session

To prevent the session from expiring, formcycle uses a keep-alive mechanism. This mechanism sends a message to the server every five minutes and refreshes the session. However, the session may expire if continuous communication with the server is no longer possible while the form is being filled out.

A timeout can occur in the following scenarios:

logging off the PC or switching to energy-saving mode
unstable or no Internet connection (especially relevant for mobile devices)
switching the IP-adress (reference to the session is lost)

The session timeout can be further extended in the Tomcat settings. The duration of the session refers both to filling out the form and to processing the forms in the formcycle-backend.