Idle Timeout Management

The app monitors your activity once you open a warehouse task. If there is no interaction (e.g., touch, swipe, or tap) for a certain period, the session will automatically close. This feature is designed to ensure that inactive sessions don’t remain open unnecessarily. If you stay idle for a predefined period, the app will automatically log you out, ending the session.

The idle timeout is considered from the R2 Configuration module. If the idle timeout value is not set / empty / zero in R2 configuration module, PackNShip app will enforce a default timeout of 30 mins.

The session timeout feature applies to the following workflows:

• Prep

• Ship

• Return

The Batch Return and Item Lookup workflows do not have the session timeout feature enabled. These workflows will continue to stay active, regardless of inactivity.

When your session times out due to inactivity, the app will display a red notification informing you that your session has closed.

• The session will continue to be tracked even if you minimize the app or put it in the background. The timeout period will still apply If you remain inactive for the timeout period, your session will still close, and you will see inactivity message when you bring it to active.

Syncing and Saving Changes After Timeout

• If you made any changes during your active session, such as modifying orders or inventory, those changes will still be saved or synced to the respective order and inventory systems. This ensures your progress is not lost after the session ends.

Order Lock Release After Session Timeout

• If you were editing an order that was locked, the app will release the lock on the order after the session times out. This makes the order available for others to edit, ensuring no conflicts in order management.

• The lock will only be released after the last user session is closed. If multiple users are working with the same order, the lock will only be released once all their sessions have ended.

Limitations

1. When typing on the on-screen keyboard, only keys that can affect/change the text, such as letters, numbers, other characters (even emojis) and backspace, will be detected as user activity and will reset the timer. Other keys on the keyboard, such as shift, caps lock, alpha/symbol/emoji mode switch etc., won't be detected as user activity as these don't send characters to the textbox. They only change the mode or settings of the keyboard.

2. User activity in the PDF Print dialog of the Picklist and Delivery Receipt will not be detected because this is not part of the app and no feedback is sent to the app.

3. In iOS, when the app is minimized, brought to the background in favor of another app, or the screen is turned off, iOS suspends the app from processing and thus the warehouse session won't be automatically closed after the specified timeout. The warehouse session will be closed when the user reopens the app after the timeout period.

4. When the user forcefully closes the app (by swiping up) in either Android or iOS, the warehouse session won't be automatically closed after the specified timeout. It will be closed when the user reopens the app.

Note: Some Android phones still offer buttons in the navigation bar as an option over swipe gestures to go home, back and see the list of recent/open apps. Pressing buttons on the navigation bar is not detected as user activity - it is not part of the app, just like the keyboard. There are inconsistencies with whether swipe navigation gestures are detected as user activity or not. Here are my findings in my testing.