Resources > Troubleshooting
Troubleshooting
Diagnose Quovra issues with symptoms, causes, fixes, and expected results.
Troubleshooting
App does not build
Symptoms:
npm run buildexits non-zero.- TypeScript or Next.js errors appear.
Possible causes:
- Wrong Node version.
- Missing dependencies.
- Invalid environment-dependent code path.
Resolution:
bash
cd app
node --version
npm install
npm run lint
npm run test
npm run buildExpected result:
- Node is 20.9 or newer.
- All commands pass.
Faucet returns 503
Symptoms:
json
{ "error": "Faucet not configured" }Possible cause:
QUOVRA_FAUCET_SECRETis missing.
Resolution:
- Set
QUOVRA_FAUCET_SECRETin the server environment. - Restart the app.
Expected result:
POST /api/faucetreturns a devnet signature.
Faucet returns 429
Symptoms:
json
{ "error": "Please wait 27s before requesting again." }Possible cause:
- Wallet cooldown active.
Resolution:
- Wait for the reported time.
- Retry once.
Expected result:
- Faucet mints after cooldown.
Deposit fails
Symptoms:
- Wallet transaction fails.
- Program returns
MarketClosed,BelowMinimum, orOutcomeLocked.
Resolution:
- Confirm market is open.
- Deposit at least 0.10 USDC.
- Use the same side for top-ups.
- Confirm wallet has test USDC.
Settlement fails
Symptoms:
- Keeper live mode transaction reverts.
- Error mentions stat, fixture, proof, or txoracle.
Possible causes:
- Proof is unavailable.
- Proof is for a different fixture.
- Proof uses a different stat key.
- Txoracle rejects the proof.
Diagnostics:
bash
cd app
npm run keeper:settleExpected result:
- Dry-run shows whether the proof is available.
Claim fails
Symptoms:
NotResolvedNotAWinnerAlreadyClaimed
Resolution:
- Wait for settlement.
- Confirm the wallet was on the winning side.
- Do not submit duplicate claims.
Related pages
Search keywords
troubleshooting, faucet 503, faucet 429, deposit failed, settlement failed, claim failed
Last updated: [YYYY-MM-DD]