found in the key ring. Get these errors a lot in my logs with no rhyme or reason. I have witness surface controller forms seemingly fail occasionally - just reloads the page. But I can't reliably recreate. Could it be Azure migrating the servers? Is there anything I can do to avoid this?

Hi @SiempreSteve From my understanding we don't need to set the antiforgery token in the form anymore nor on the controller, it just gets done magically for us. I think i had this error when trying to add an antiforgery token to the form myself.

I checked that too. I pretty sure I'm not doing that. It was "merged" v7 code. So I will have a triple check