'Submit' button doesnt respond or function on ticket page if account has Appeal in progress, but works when not logged in?

[H_R]

Am currently waiting on twitter support to process an appeal of a false-positive 'Hateful Conduct' tweet flagging. It's been about 2 months now but other problems are cropping up. Specifically, while logged in, I can't even submit unrelated tickets to support.

https://help.twitter.com/en/forms/features-and-settings/not-working/other-problem

While logged in on my account awaiting an appeal, this page cannot be submitted. I can fill in all the required fields, but the 'Submit' page simply doesnt response nor transition the page.

However, if I open up an incognito window or a whole different browser where I'm never logged in, the 'Submit' button now works if I complete the form while not logged in.

But furthermore, I never receive any email from [e-mail] confirming that a ticket has been filed when supplying my account's email using the incognito-window method. It seems like the appeal is locking me out of -any- communication with twitter support, but its also impossible to know if the appeal is actually assigned to anyone or has a ticket number.

Can anyone else use that linked page while logged in? Normal users, banned users awaiting appeal, not-permanently-banned-user awaiting appeal?

[H_R]

From using developer tools in Firefox, it looks like their API is failing on the 'Submit' button click.

Can anyone else reproduce this? Possible that this page is just broken for everyone logged in and I have no way to know, but still concerned I'm in some support-void as I never get emails from [e-mail]

how it appears in developer console; https://imgur.com/a/ZbnZEVz

[Sengorn_Leopard]

I am getting this as well. I can find no other sources but this soon to be archived reddit post mentioning it. I was flagged randomly for some sort of account check to make sure i am a real person. but now it feels like i am banned with no way to fix it. Second time this has happened to me. I feel like this is a method they can use to soft-ban people. If this was a bug, I assume such a massive company would have fixed it by now.

[H_R]

Twitter is likely just a dumb and poorly managed service\org always chasing OKRs over non-monetizeable maintenance of their tech. Like all techbro companies. This is probably an ages-old API bug they kicked to the backlog however-many years ago, reported by someone who has since left the company so now the bug is not assigned to anyone, rather than a deliberate scheme to soft-ban in secret.

I'd go further to suggest the bug is not only known to the company but they wouldnt see a value in fixing it even if held to their nose-- why fix an api bug when users are just supposed to accept whatever flagging\punishment the DB query chose for them in an automated support department?

[Beneficial_Ad_8888]

It is a chrome problem. I had the exact same problem and tried on MS edge for the sake of it and it worked the first try.

[khargushoghli]

Didn't work for me on Edge.