Critical Loop Bug: Enterprise account "injazsoft" stuck in automated suspension loop (Ticket #4399178)

[saudhezaminjazsoft]

🏷️ Discussion Type

Question

Body

Hi GitHub Community Management,

I am opening this new discussion as a critical update because our situation has escalated to an absolute business emergency. Our enterprise account 'injazsoft' has now been trapped in an automated suspension loop for 28 consecutive days.

Two weeks ago, we opened discussion #196337 regarding this issue. We strictly followed the advice given to us: we stopped opening new tickets to avoid confusing the queue, and as recommended, we reached out to @githubhelp on platform X (formerly Twitter) over two weeks ago.

Unfortunately, we have received absolutely no response on platform X, and our master ticket #4399178 (escalated by Brendan 17 days ago) remains met with total, unbroken silence, leaving our entire business and development team completely paralyzed.

We want to emphasize that we completely respect GitHub's security, compliance, and safety protocols. We are a legitimate enterprise and are not seeking to bypass any required security checks or standard verifications. However, 13 days of complete silence on an escalated ticket is causing severe operational and financial damage to our business.

We desperately need a community moderator to intervene and flag this ticket internally to the compliance engineering team. We just need a human review to investigate this automated re-flagging bug and apply a permanent manual exclusion to our organization ID.

Thank you for your urgent help and understanding.

[NicolasVitorP]

Hi there. I am incredibly sorry to hear that your enterprise is going through this. Having your entire development team and operations paralyzed for nearly a month due to an automated suspension loop is an absolute business nightmare, and your frustration is completely justified.

While the GitHub Community Forum is primarily a peer-to-peer space and community members don't have access to internal ticketing systems, accounts, or compliance data for security reasons, your situation definitely warrants immediate internal visibility.

Since you have already followed all the correct steps (keeping a single master ticket #4399178 and reaching out to the social channels), here is the best way to leverage this forum:

1. Keep this specific thread open: Do not open duplicate discussions, as the automated system or moderators might close them as spam, which hurts your visibility.
2. Wait for a Community Moderator flag: Official GitHub Community Managers and Moderators routinely scan this specific section. When they see a critical corporate blocker with specific ticket numbers like yours, they have the internal channels to escalate or ping the verification/compliance queues directly.

I am upvoting this discussion to help boost its visibility in the feed. Hang in there, and I truly hope a community manager catches this thread shortly to get your business back online.