When is Nextworld going to provide a warning to users before auto logging them out after an 8 hour period

Sorry - I’m not sure this is the correct category but it seemed to be the best fit.

Users get kicked off the system after a period of time (I’m not positive on the # of hours but think it is around 8) without getting any warning. Why can’t users get a warning before this occurs. This often impacts developers and work is lost.

I am not sure the answer on if/when we will provide a warning before logout, but I can say that no work should be lost if your developers get logged out after inactivity.

Our platform has built in functionality to auto-save your work every 7-8 seconds after a change is made, and if your browser crashes, you accidentally close the browser tab, etc. Your work will be saved under the Pending Work section of the relevant application, which is accessible in two ways:

  1. The yellow Pending Work icon in the upper lefthand corner of the application next to the name of the app.
  2. In the hamburger menu under the Pending Work or Save for Later sections while the relevant app is launched.

This functionality should allow your developers to recover the latest draft of their unsaved work in this scenario. Hope this helps!

2 Likes

This request is currently being tracked in our backlog and will be considered for an upcoming release. For future reference, this request is being tracked under BOTPLAN-22346.

1 Like

FYI, by default, Nextworld sessions time out after 10 hours. The maximum session length is 12 hours, minimum is 1 hour, and is configured at the tenant level by Nextworld administrators. Please consider submitting a ticket requesting an increase to 12 hours for the Environment(s) where you are seeing an 8 hour timeout.

1 Like

Thanks for the responses, everyone. Ian, to clarify, our concern isn’t really about the specific timeout duration—be it 8, 10, or 12 hours. Instead, it’s the sudden and unannounced nature of the session logoff that’s causing issues for both our developers and our customers. We can certainly explain why session logoffs are necessary, but it’s challenging to explain to customers why they don’t receive a brief warning beforehand. We believe that providing a warning would be a more user-friendly and standard practice.

@Bill.Hylton agreed and understood. The request for a warning prior to session timeout is very valid.