Sometimes When Updating Records Browser Shows: Security Warning: Your submission token does not match session tokenIssue Sometimes when updating records browser shows: Security Warning: Your submission token does not match session token. This occurs when: You are performing an actionYour session has expiredHigh security plugin is enabled (with CSRF protection) ReleaseApplies to all environments.CauseYou are seeing that message since you have Cross-site Request Forgery (CSRF) prevention tokens enabled.ResolutionPlease note that this is a security feature in our platform which we recommend to be enabled in all instances. Please also note that a token (Browser cookie) is issued when a user logs in and is set to expire after a set amount of time (86400 seconds or 1 day). You will see this message if a user's token expires but does not get cleared from their browser's cache. Please be advised you would need to log out and log back into the instance to set a fresh token. For additional reference, these are the parameters the you have set on your instance. Please kindly note these details as they are the recommended settings according to our Instance Hardening KB article KB0550654 - glide.security.use_csrf_token: true - glide.security.csrf_previous.allow: false - glide.security.csrf_previous.time_limit: 86400 - glide.security.csrf.strict.validation.mode: false You could disable the message entirely by setting 'glide.security.use_csrf_token' to false, however We *DO NOT* recommend that you do this. Alternatively, by setting 'glide.security.csrf_previous.allow' to "true", this would allow you to continue using an expired token. This is also not recommended but it would stop the alert. We would recommend for you to simply log out and log back in to the instance if you see this message again.