Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Error 'Possible CSRF attack detected!”

We have noticed this error intermittently when trying to view our polices and schedules.

When this error does occur, would the alert process still work?

1 answer

1 accepted

2 votes
Answer accepted
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Nov 12, 2021

Hi @William Butt ,


This is just a front-end browser related error, it will have no impact on the alerting process in Opsgenie.


This can happen when sessions are reset causing stale cookies to be leftover. Refreshing/logging back in should clear the issue. Can you try refreshing your browser, and clearing cache/cookies and see if the error comes up?




Thanks Samir,

It's been happening frequently for the past three days and it's happening with other collogues of mine as well.

Very happy that this will not impact on the alerting process.

I have cleared our cache and the error hasn't come up since.

Thank you again Samir.

Like Steffen Opel _Utoolity_ likes this

i cannot schedule a maintenance policiy in windows 11 due to this error.

What cache did you clear Wiliam?

Thanks all. Jan-Willem

Hi Jan-Willem,

I just cleared my browser cache. I had to do this on Edge and Chrome.

I have found in my instance that I still get the error however, I just then refresh my browser to clear the error. or a reload of the page, that stops the error again.

Hope that helps.

Thanks so much @William Butt

Clearing cache did it. Was the first time I had this issue and appeared just after updating to Windows 11. I do have to say I haven't scheduled a maintenance policy since about 2 weeks. So it might have nothing to do with the update.

Have a great remainder of your sunday!


You as well @Jan-Willem Aikens

I must say that seeing a message with the work '... attack'... in it did not even remotely make me think of clearing browser cache :)

Like Jan-Willem Aikens likes this

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events