Overview
This article addresses the "token has invalid claims: token is expired" error that may occur when attempting to save a test case after a long recording session in the Architect.
How It Works
When a test case recording begins, a security token is generated to authenticate the session. This token has a specific, limited duration for security purposes. If the recording process, including any idle time, exceeds this duration (for example, lasting more than 30 minutes), the token will expire. Attempting to save the test case with an expired token results in an error, as the system can no longer validate the session.
Limitations
This behavior is an expected part of the system's session management and is not considered a functional defect. The occurrence of this error is tied to the session duration and may not be consistently reproducible. It is a security measure to prevent unauthorized actions from an old or abandoned session.
Related Info
To prevent this error and ensure your work is saved successfully, please follow these best practices:
- Begin recording your test case soon after logging into the platform.
- Avoid extended idle periods while the Architect is actively recording.
- If a test case is particularly long or complex, consider breaking it down into smaller, more manageable tests to avoid session timeouts.
- If you encounter this error, the recorded steps cannot be saved, and you will need to start the recording process again.