Skip to content

Solutions

Fix it yourself

Straight answers to the problems SolveLang customers actually run into — what you see, why it happens, and the exact steps that fix it. Every fix below is one you can apply yourself, in your own account or your own workflows.

My own runners take every job — how do SolveLang runners get work?

Route chosen pull requests to SolveLang with a label, so your own fleet and SolveLang share the work the way you decide.

How minutes and metering work

Per-second billing from the job's own start and finish times, a 10-second minimum per job, and the Spot and On-demand multipliers explained.

The payment area showed an error when I switched packs

Switching packs during one checkout used to break the payment area. It is fixed — and an unfinished payment is never a charge.

I added a repository after installing, but it did not connect

GitHub does not tell the app when you change an existing installation's repositories. Re-run the connect flow to add the new repository.

Pause and resume your runner minutes

Pausing stops new SolveLang machines from starting — without losing your balance. Resume from the same control whenever you are ready.

Labels and pools: Standard vs High-Power

Your workflow's runs-on labels choose the pool: Standard for everyday machines, High-Power for larger, faster ones. Each pool has its own balance.

Sign-in link problems

The two usual traps: a sign-in email that never arrives, and a sign-in that loops back to the form — and how to fix both.

Where to see your balance

Your account home and the Live Center Minutes tab both show the Standard and High-Power minutes you have left, with the earliest expiry.

Still stuck? Email hello@solve-lang.com or browse Support for the scanner, plugin, and report guides.