If the limit of actions per access is reached, what happens to the user session?

When the limit of actions per access is reached, the user session is ended. This is typically designed to safeguard system resources and ensure that users do not overload the system by executing an excessive number of actions within a single session.

Ending the session effectively logs the user out or terminates their access, which is a common approach in many systems to manage performance and maintain stability. This mechanism is often implemented to prevent abuse or accidental overload by restricting how much a user can do in one go, allowing for a more controlled and reliable user experience.

In contrast, pausing a session, prompting the user to continue, or leaving the session active would not effectively address the limits set for user interactions and could lead to complications or degradation of service in the system. Hence, ending the session is the most logical and practical approach when the specified limit is reached.