Skip to main content

​
Troubleshooting

​
Money-saving checklist

These options do not consume Compute Credits or reduce usage significantly — use them in order: Prefer manual edit for small changes： Text, colors, layout — use Manual edit at zero Compute Credits instead of Execute now every time. Lock scope before execute： In Free consultation, agree what page / feature to change and what not to touch; vague asks (e.g. “everything feels slow”) can expand into a whole-app pass and spike usage. Review the plan; avoid over-building： After you confirm to-dos, remove items you don’t need before execute; say “simplest path, only do X, don’t touch other modules.” If scope is unclear, consult first so a “medium” change doesn’t expand into a multi-module build that burns time and Compute Credits. Reuse marketplace when you can： Remake a close App marketplace listing, then edit — often cheaper than rebuilding from scratch. Consult before execute： See Consultation guide. Start in Free consultation： Questions in execute mode cost Compute Credits; click Free consultation first for free discussion. Stuck in a fix loop： See Feature fix troubleshooting guide. More ways to avoid unexpected charges: Pricing → “Reduce unexpected charges”.

​
Why can a small change cost a lot of Compute Credits?

Usage depends on complexity and blast radius, not only visible diff size. Changing copy is usually small; changing login, permissions, database fields, or checkout flows — even in one sentence — may touch many pages, APIs, and schemas. Surface size alone is not a reliable estimate. Broad wording (e.g. “optimize everything” / “all clients feel slow”) can also expand into a large scope that looks like a “small tweak” but is not. Before execute：
  1. Describe the need in Free consultation, and state what to change and what not to touch.
  2. Ask the AI for affected pages, data, and features; confirm the blast radius is acceptable.
  3. Request a step list or todo breakdown.
  4. Confirm scope, then execute; prefer Manual edit for two-line copy or style tweaks.
  5. Batch related changes in one feature to avoid repeated project re-reads.

​
Break down first, execute second; roll back if you break something

To save Compute Credits and reduce rework:
  1. Free consultation first Click Free consultation and ask Su Xiaoqiang for scope, impact, and steps; execute only after alignment.
  2. Upload action video or screenshots For UI state, paths, or repro steps, use Upload action video in attachments or key screenshots — clearer than text alone.
  3. Roll back, then small steps If a change breaks other features, do not keep patching blindly. Use Version history, restore a stable version, consult again, then execute in smaller scope.
  4. One issue at a time Name page, feature, and expected outcome; avoid “while you’re at it” scope creep.

​
Session issues after topping up Compute Credits

Session oddities after top-up? Check logs → Troubleshoot → retest. Steps：
  1. Logs： Check system logs for post–top-up errors
  2. Troubleshoot： Use Troubleshoot in superun for abnormal state
  3. Retest： Verify the session continues normally
Prevention：
  • Check account status before top-up
  • Allow a few seconds for balance sync after top-up

​
How to save Compute Credits

Symptoms：
  • Simple edits cost too much
  • Repeated fixes burn Compute Credits
Fixes：
  1. Manual edit： Style tweaks via Manual edit (zero Compute Credits)
  2. Consultation： Click Free consultation for planning (free)
  3. Troubleshoot： Try Troubleshoot first (free)
  4. Invite users： Invitees who complete demo can earn 20 Compute Credits
  5. Stop early： Do not keep spending on a wrong direction
Comparison：
  • ❌ Chat to change styles: costs Compute Credits
  • ✅ Manual edit: zero Compute Credits
  • ❌ Execute features directly: costs Compute Credits
  • ✅ Consultation planning: free
  • ❌ Manual debug in chat: costs Compute Credits
  • ✅ Troubleshoot: free

​
Insufficient Compute Credits and service shutdown

Symptoms：
  • Balance too low; cloud services auto-stopped
  • Empty project after login
  • Features unavailable
Fixes：
  1. Top up： Recharge on Account
  2. Auto recovery： Services restore after top-up
  3. Manual recovery： If not restored, say redeploy in chat or click Troubleshoot for automatic redeploy
After cloud recovery, database connection URLs may change. If data access fails, say redeploy in chat or click Troubleshoot.
Important：
  • Overdraft： 50 Compute Credits overdraft lets you continue briefly when balance is low
  • Data retention： If balance including overdraft hits zero, project data may not be retained
  • Data recovery： To recover shut-down project data, contact enterprise WeChat support and pay recovery fees if required
Prevention：
  • Monitor balance for steady service
  • Act on low-balance SMS reminders
  • Plan usage; keep 50–100 Compute Credits buffer when possible
Related：
  • superun cloud hosting: about 3.5 Compute Credits/day per published project
  • Overdraft: 50 Compute Credits
  • See Pricing

​
Cloud service fees

Rates：
  • Each published project: about 3.5 Compute Credits/day (~105/month)
  • File storage: base 1 Compute Credits/day plus usage — see Pricing
What it covers：
  • Not just hosting — includes compute, storage, SEO, and related services
  • Varies by project usage
View charges：
  • Account → Usage history for line items
  • My Compute Credits → Usage details → Project details for per-project usage, cost breakdown, and skill timestamps/sources
Estimate：
  • Small published app: about 195 Compute Credits/month (Compute Credits, cloud, storage combined)
  • Keep at least 100 Compute Credits for stability

​
Top-up display delay

Symptoms：
  • Balance mismatch after top-up
  • Record shows but balance unchanged
Fixes：
  1. Wait： Sync usually takes a few seconds
  2. Refresh： Reload the page
  3. Records： Check Compute Credits details on Account
  4. Support： Contact enterprise WeChat support if it persists
Prevention：
  • Check account before top-up
  • Wait a few seconds after payment

​
Top-up refunded / bank transfer not received

Corporate or bank transfers may bounce if payee details changed. Place a new order for updated bank details, then transfer and wait for authorization; contact enterprise WeChat support if funds do not arrive.