Limits of Ansys Account Credential Expiration Handling

The goal is to determine the exact behavior of Ansys desktop solvers (e.g., Mechanical, Fluent) when an Ansys Account credential used for cloud entitlement or license checkout expires while a solve is in progress.

Constraints include the absence of documented least‑privilege role‑based controls inside the solver, reliance on FlexNet for binary license availability, and the fact that expired credentials may be cached locally, leading to product‑ and version‑dependent prompts for re‑authentication.

Does the solver immediately reject new license checkouts, allow the current solve to finish, or silently fail? How long after expiration does the client prompt for new credentials, and does this interval differ between on‑prem license servers and Ansys Cloud? Is there a configurable timeout or policy to force re‑authentication without restarting the solve?