Unresolved
As of 2026-11-17

All 66 cases

Documented case · 2025

maayan-frontegg (account @frontegger-s1)

Flagged Dec 29, 2025

UnresolvedNot statedOAuth lockoutCode access lost / 404

Verified primary source

The account holder's own post, discussion or thread was opened and read in full for this entry.

A dedicated QA automation account, flagged with the exact error that runs through this explorer: "This account is flagged, and therefore cannot authorize a third party application." For a QA account whose entire job is testing OAuth flows, that error is not a limitation; it is the whole job removed. Her Community post was closed by staff with a redirect to Support, which is where the public record ends.

The record

Suspended or flagged
Flagged December 29, 2025
Posted
GitHub Community discussion #183072, December 29, 2025
Ticket / discussion
Discussion #183072; staff closed it and redirected her to Support
Suspected trigger
Not stated. The account is used for QA automation and testing, including OAuth flows, and she believes the flag is a mistake
Human reply from GitHub
No: staff closed the Community discussion as not a support forum and redirected her to Support; no resolution is in the thread
How it ended
Unknown; no resolution in the thread
Duration
Not stated

Suspected triggers are the account holder’s inference, never GitHub-confirmed, unless the record above says GitHub stated or confirmed it. A suspension does not by itself prove GitHub made a mistake.

Sources

First-hand GitHub Community discussion #183072 by maayan-frontegg; opened and checked November 17, 2026.

This entry is one of 66 in What Kind of Life Does a Flag Preserve?, a documented account of GitHub suspending a fourteen-year-old developer account and the same pattern repeating across the industry. If the same thing has happened to you, the article’s eight-step playbook is built from what actually moved these cases.