- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-09-2025 10:15 AM
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-09-2025 10:19 AM
Hi,
No need to worry about this. This happens because your previous session has expired. You can still go ahead with your work. Log in to your instance and continue your work.
Thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-09-2025 10:17 AM - edited 07-09-2025 10:21 AM
@ambikagoyal Is it happening only for specific BR or for all Business Rules?
Try clearing the cache using cache.do for instance and relogin and check. This happens because your previous session has expired.
✔️ If this solves your issue, please mark it as Correct.
✔️ If you found it helpful, please mark it as Helpful.
—
Shubham Jain
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-09-2025 10:19 AM
Hi,
No need to worry about this. This happens because your previous session has expired. You can still go ahead with your work. Log in to your instance and continue your work.
Thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-09-2025 10:25 AM
Hi @ambikagoyal ,
this comes up when the session is expired and you login again and try to update a record in a page which is not reloaded and still holds the old session id
1. you can ignore it whenever the session is expired and you login again reload the page and update or perform you action
2. you can try setting below property to false
glide.security.csrf.strict.validation.mode
I would go with 1 option
Please mark my answer as helpful/correct if it resolves your query.
Regards,
Chaitanya