-
Notifications
You must be signed in to change notification settings - Fork 243
[47854] - Session Destroyed automatically . #8695
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: develop
Are you sure you want to change the base?
Conversation
….js; enhance Session.vue to utilize session state updates and warnings. This includes adding BroadcastChannel support for session events, localStorage management for session state, and integrating session renewal logic in the Session component.
…bootstrap.js; update Session.vue to handle session expiration and logout functionality with improved button interactions. Modify session.js to ensure proper handling of timeout warning seconds.
|
QA server K8S was successfully deployed https://ci-4956f1abde.engk8s.processmaker.net |
|
QA server K8S was successfully deployed https://ci-4956f1abde.engk8s.processmaker.net |
|
QA server K8S was successfully deployed https://ci-4956f1abde.engk8s.processmaker.net |
…ion event handling; improving performance and user experience during session management.
…rap.js and Session.vue; update broadcast logic to synchronize logout state across tabs, improving user experience during session termination.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.
|
QA server K8S was successfully deployed https://ci-4956f1abde.engk8s.processmaker.net |
|
QA server K8S was successfully deployed https://ci-4956f1abde.engk8s.processmaker.net |
|





Issue & Reproduction Steps
The session loss warning when you have multiple tabs does not correctly control the time of each one; the time should be global and synchronized for all of them.
Solution
How to Test
Log in to the ProcessMaker platform.
Open multiple browser tabs, such as:
Editing a screen
Editing a script
Editing a process modeler
Viewing a request page
Work on one of the open screens while leaving the other tabs idle.
After 5–10 minutes, the session automatically expires some time take more than.
When you try to submit changes, an "Unauthorized" message appears, along with a "Stay Connected" prompt.
If you do not click "Stay Connected" or miss the prompt, you are automatically logged out.
As a result, any unsaved changes in screens, scripts, or process models are lost.
Related Tickets & Packages
Code Review Checklist
ci:deploy
Note
Unifies and synchronizes session timeout handling across tabs with a new shared module and UI updates.
common/sessionSync.jsto manage the timeout worker, leader election (viaBroadcastChannel/localStorage), and cross-tab events:warning,renewing,renewed,started,activity,logout,expiredbootstrap.jsandnext/config/session.jswithinitSessionSync, wiring inEcho, notifications, and modal getters; exposessessionSyncand timeout vars globallycomponents/Session.vueto show a processing spinner during renewal, broadcast renewal/logout/expired, update shared session state, and restart worker only when leadersessionIsRenewingstate to navbar (classic and Next) and passes it to<session-modal>in Blade; ensures closing the modal clears renewing stateWritten by Cursor Bugbot for commit df25a80. This will update automatically on new commits. Configure here.