Issue Description

After deleting the API token, the token still persists in the cache. Despite the deletion process, the token remains accessible until the page is manually reloaded. This inconsistency poses a potential security risk.

Also, the 'Token expiration date' field is not clear after successfully creating the API token.

Steps to Reproduce

1. Log in to the app,
2. Navigate to the settings or profile section where API tokens are managed.
3. Create a new API token.
4. Then delete that API token.
5. Notice that the deleted token is still accepted and functional.
6. Manually reload the page to remove the token from the display

Expected Behavior

The API token should be immediately removed from the cache after successfully deleting it from the database.

Current Behavior

The API token remains accessible and functional even after deletion until the page is manually reloaded.

Screenshots (optional)

Operating System [e.g., Windows 10]

Windows 11

Browser [e.g., Chrome, Firefox]

Chrome, Edge

Version [e.g., 2.0.1]

Latest

Please check the boxes that apply to this issue report.

• I have searched the existing issues to make sure this is not a duplicate.
• I have provided steps to reproduce the issue.
• I have included relevant environment information.
• I have included any relevant screenshots.
• I understand that this is a voluntary contribution and that there is no guarantee of resolution.
• I want to work on creating a PR for this issue if approved