Troubleshooting

"This run ran out of time" (SMX-E01)

Every run has a fixed wall-clock budget (well under Vercel's platform function limit, by design). Very long or unusually complex decisions can exhaust it. Your credit is refunded automatically — try again, or split the decision into a narrower question. See Stopping a run.

"Providers are congested" (SMX-E02)

solvemax routes across a pool of model providers with automatic failover; this error means the whole pool was unavailable or overloaded at that moment — rare, and almost always transient. Your credit is refunded; retrying shortly usually works.

My slip says UNAUDITED instead of CONFIRMED

This is not an error. It means the independent verification pass didn't finish inside the run's time budget, so the slip shipped honestly labeled rather than the run being failed and refunded for a deep analysis that already succeeded. See Confidence & verification — the winner shown is the deep run's own pick, not a confirmed second opinion, and the slip says exactly that.

My anonymous run vanished / I can't find it after signing in

Claiming only works automatically on the same browser you ran it on (it reads a local list your browser kept). If you switched devices, use the direct slip link instead of relying on auto-claim — see Claiming runs.

"Free runs cap at 6,000 characters"

You're on the anonymous or free-signup-credit tier. Signing in with a paid credit raises the limit to 20,000 characters. See Writing a good decision.

"Too many runs from this network"

The free-tier per-IP limit (6 runs/hour) has been hit — common on shared networks (offices, coworking spaces). It resets on a rolling hourly window; paying customers are exempt. See Rate limits.

My API key returns 401

Confirm the key hasn't been revoked from your dashboard, and that the Authorization header is exactly Bearer smx_live_... with no extra whitespace. See Authentication.

I was charged but didn't get a credit

This shouldn't happen — credits are granted only once Stripe confirms payment, not at checkout initiation. If it does, contact support with the checkout session or subscription id; this is treated as a P0 billing issue.

A completed run's numbers look odd (e.g. an option scored 0)

A dash (—) instead of a number in the scored matrix means that criterion genuinely wasn't scored for that option, not a zero. Criteria marked "(cost)" are inverted — lower is better — which can look surprising at a glance if you're expecting higher-is-always-better.