---
title: "User Auto-Logout Before Performing Check-Out"
description: "Problem Statement A user successfully checked in on a given day (for example, in the morning at 8:00 AM). However, when the user attempted to check out later (around 8:00 PM), they found that they had been auto-logged out of the application without ..."
url: "https://supportb.kinsta.cloud/docs/user-auto-logout-before-performing-check-out/"
updated: "2025-10-22"
category: Mobile Application
---

# User Auto-Logout Before Performing Check-Out

### **Problem Statement**

A user successfully checked in on a given day (for example, in the morning at 8:00 AM). However, when the user attempted to check out later (around 8:00 PM), they found that they had been auto-logged out of the application without performing the check-out.

### **Possible Cause**

This situation may occur due to a **soft logout**, which happens when the user’s authentication token expires.
 Token expiry can occur for several reasons, such as:

- Changes made in the authentication configuration
- Log in from another device using the same credentials
- Backend token expiry.
- ### **Steps to Check**
  1. **Verify Check-In and Check-Out Records**
     - Navigate to the **Check-In/Check-Out Report History**.
     - Confirm if the timestamps and records match what the user has reported.
     - Note any missing or incomplete entries around the time of the reported issue.
     - Also, ensure that the check-out is made mandatory before the user  can log-out 
  2. **Review User Login History**
     - Open the **User Login History** section.
     - Cross-check if there are any discrepancies between login and check-out times.
     - Check if there are multiple login attempts or logins from another device or browser around the same time, which could have led to the earlier logout.
  3. **Check User Audit Logs**
     - Review the **User Audit Log** to see if there have been any recent changes related to authentication (e.g., password change or request change).
  4. **Raise it to Engineering team**
     - If all the above checks are completed and there are **no signs of multiple user logins, authentication changes, or discrepancies in report history**, reach out to the **Engineering Team** to verify from backend logs whether a **soft logout event** occurred for the user.