Troubleshooting

• Check whether the original Hugging Face page opens. An outage or rate limit can affect requests.
• Clear overly narrow search, category, or size filters. Missing size metadata can exclude a model from size-filtered results.
• Retry the failed request after the service’s indicated wait, rather than repeatedly refreshing.
• A loaded count is not the total Hub catalogue. Use Load more for additional results.
• A missing profile count is unavailable data, not a page error that should be replaced with zero.

Sign out and start a fresh Hugging Face sign-in if the session expired or your organization role changed. Check you are using the account that controls the repository’s namespace.

For organizations, Hugging Face must report admin or write access. A read-only role, verification badge, or contribution does not qualify. Private repositories and models outside the selector’s fetched batch may not be listed.

Use PNG, JPEG, GIF, or WebP at 2 MB or less. Confirm that the browser can read the file and that the preview matches it. Changing the extension is not a format conversion.

Preparation stops if public media storage is unavailable or metadata cannot be reached. Use the launch page’s setup status and Check again after the service is restored. A local picture preview is not proof that the public upload succeeded.

The form must have complete token details, verified repository access, a mainnet connection, and a connected payer wallet. Read the actual error, check your SOL balance, and correct the named issue before preparing again.

Preparation alone does not broadcast a launch. A simulation or fee-estimate failure prevents signing. If the preview expires before submission, prepare a fresh transaction; do not sign an expired preview.

Rejecting a signature request does not authorize the launch. If there is no recorded submitted signature, review the form and try again only when the details are correct. If a signature is already recorded, follow the confirmation steps below instead.

1. 1

   Keep the recorded transaction

   Save its Solscan link and mint address. Do not clear browser storage or start a launch in another tab to work around the pending state.
2. 2

   Check the existing signature

   Use Check confirmation in the launch form and View transaction to inspect the chain status.
3. 3

   Distinguish pending, success, and failure

   A pending result is not a success or a definite failure. A confirmed/finalized status without an execution error is success. An explicit execution error is failure.
4. 4

   Resolve before retrying

   A timeout can occur after a transaction has reached the network. Starting again while status is unknown can create a duplicate token. Wait until the existing result is established.

The metadata website always uses the Hugpad mint-address URL, but this app does not yet provide that coin-page destination. After confirmed creation, use the pump.fun coin link and Solscan transaction link. A missing Hugpad page is not evidence that the Solana transaction failed.

Share the visible error message, the step you reached, the repository ID, and the public transaction signature if one exists. Never include an access token, API key, seed phrase, private key, or a screenshot exposing sensitive account information.