BC-0294 · TROUBLESHOOTING
Editorial review 2026-09-27
Is This a Moderation Problem or a Build Bug?
Use the actual notice and failed stage to distinguish moderation from an unexplained technical problem. A named policy action supports the moderation route; a spinner, missing button or inaccessible link alone does not. The possibilities can coexist, so resolve each observed boundary without guessing a single cause for everything.
Symptom
The creator is unsure whether a failure is a policy decision, a technical issue or overlapping problems.
Immediate action
Separate explicit decision evidence from unexplained interface behavior and preserve both contexts.
Diagnostic branches
- A specific policy action is stated.
- Use its official process for that affected object.
- A technical failure blocks responding to a stated action.
- Report the response-path failure separately without treating the policy action as reversed.
- No policy notice exists.
- Use the observed symptom and leave moderation unconfirmed.
Least-destructive change
Preserve evidence and avoid speculative keyword changes, repeated submissions or evasion experiments.
Retest
- Every classified policy action has actual notice evidence.
- Separate failures are not forced into a single unsupported cause.
- Later evidence is dated in the sequence rather than rewritten into the original observation.
Escalation
Use official assistance with both the notice and any distinct interface error when appropriate. The guide cannot determine an unseen moderation reason or overturn a decision.
Working notes
Preserve exact wording and context. A notice naming an affected object and action is different from a generic error. Do not remove important qualifiers when paraphrasing it, and do not infer a hidden violation category from a failed request with no explanation.
Follow an explicit policy or account process for the action it actually covers. If a separate interface problem prevents using that process, record both: the moderation action and the technical obstacle to responding. A broken appeal surface does not reverse the underlying action, while a policy notice does not prove every unrelated control failure has the same cause.
When no specific notice exists, record the last successful transition and the actual failure. Keep account, project and destination identity clear. Use the appropriate symptom guide for a bounded investigation instead of rewriting supposedly prohibited words or repeatedly publishing to probe a hidden rule.
Update the classification only when new evidence changes it. A later notice can clarify an earlier unknown, but should not be retroactively described as having been observed from the start. Preserve the sequence so official assistance can distinguish the issues.
Examples
- Coexisting issues: an actual moderation notice offers a review path, but that path returns an unrelated interface error. Record the decision and the response-path failure separately rather than claiming the decision vanished.
- Unknown case: a loading view stops without a policy message. Keep the cause unconfirmed and use loading diagnosis, not an invented moderation appeal.