Support / Work through it
A clear next step.
Start with the symptom. Keep your design files private.
Something isn’t running
Queued jobs, missing results, storage changes and first checks.
Open troubleshooting ↗02 / AccessSign-in or activation
Account approval, license selection, refresh and device release.
Read the activation guide ↗03 / AccountPurchases and billing
Check your owned licenses and use the available billing controls.
Open purchases and billing ↗Make it reproducible
A useful bug report
starts with the facts.
Record the app version, what you tried, what you expected and what happened. A small, repeatable example is more useful than an entire project archive.
Draft a useful report
Fill only what helps explain the issue. Drafts stay in this page’s memory with no saved copy; reload to clear them. Nothing is submitted automatically.
Application troubleshooting →Version and topic details (optional)
Preview what gets copied
Axial Flux Studio support draft Topic: Application or installation Report summary: [add] Expected behaviour: [add] What actually happened: [add] Reproduction steps or checks already tried: [add] App version: [add from Settings] Windows edition/build: [add] Visible safe error code: [add] Prepared locally on /support. Review before sharing; remove keys, tokens, private paths and confidential design details.
Recipient: [email protected]
Open draft in your email app →Review the preview before copying or opening email.
A result looks wrong?
Include the solver, mesh, current convention and study type. Check that the compared quantities use the same units and conditions before treating a difference as a solver bug.