Publish held or rejected
When you publish a game, it passes through a series of automated checks
before it's live. This article explains how to read the result and what to
do if a publish is held or rejected.
Reading the publish timeline
Your publisher dashboard's Publishing tab shows a gate-by-gate timeline for
each publish — every check that ran, in order, with its outcome. A publish
that's still in progress shows which gate it's currently at; a completed one
shows exactly which gate stopped it, if any did.
Held vs. rejected
•
Held means a check flagged something for human review rather than
approving or rejecting it outright — this is not a final outcome. You can
see the reason on the timeline and respond.
•
Rejected means a check failed outright and the publish did not go
live.
Appealing
From the publish's detail page, you can open a thread with Gameweave staff
directly — explain your side, provide context, or ask what specifically
triggered the gate. A staff member replies in the same thread. This is the
right path for anything you believe was flagged in error.
Why a security gate can't be cleared
Some gates — the ones that check for things like malformed archives or
unverifiable publisher signatures — protect against threats to every player
on the platform, not just quality issues with your specific game. These
security-class gates cannot be overridden or cleared by an appeal, even by
staff: if one of these is the reason your publish was held or rejected, the
fix is to correct the underlying issue (for example, re-signing or
repackaging your submission) and publish again, rather than appealing the
gate itself.