Troubleshooting

"Sol said email was sent but it didn't arrive"

First: open the trace link at the end of Sol's response. Look at the output step. If the messageId is a real UUID (36 hex characters with hyphens), the email was actually sent — check your spam folder.

If messageId is missing or looks short/fake, the verifier should have redacted it as "[valor no verificado]". In that case, the email didn't send. Common causes:

Wrong recipient address (typo) → retry with correct email

Domain rate limit → wait 1 hour and retry

Attachment too large → reduce rows or split export

"Capability never converged"

Some sites are hard for the engine (lots of JS, cookie banners, unstable class names). Sol's explore engine has a 20-iteration budget; on complex sites it may give up.

Options:

Try a simpler alternative site with the same data

Give Sol a specific selector hint: *"Sol, aprendé ... el selector del precio es `.price-badge > span`"*

Wait for scroll + accept-cookies support (roadmap item)

Note: Sol will NEVER pretend to have learned if it didn't. "Did not converge" is honest.

"Process is stuck running for hours"

This shouldn't happen often — the engine has timeouts. But if it does:

Open the trace, check `current_step_index` to see where it got stuck

If a capability step: check the capability execution — maybe Chrome is disconnected

Email support@agas.ar with the execution_id. Staff can kill the execution and diagnose.

"Extension shows 'Connecting...'"

See [Chrome extension](/help/extension) troubleshooting section.

"I asked for X but got Y"

Sol's interpretation of your intent might be off. The response should say what it planned to do (via the plan summary). If plan ≠ intent:

Say what you actually wanted more explicitly

If you asked Sol to compose a process, it might have added an unnecessary step. You can ask: "correlo sin el analyze step" — the composer will redo it.

"Canary failed twice, capability marked needs_human"

The engine couldn't produce a reliable recipe for this site. Options:

Give Sol a more specific prompt with a selector hint

Try a different entry URL on the same site (e.g. a category page instead of the home)

Archive that capability and look for an alternative data source

"I'm over my exploration budget"

Exploration budget caps prevent runaway costs. If you hit yours:

Check which capability is consuming tokens (trace UI shows per-run cost)

Archive capabilities you don't use

Request a temporary budget bump at support@agas.ar

"Sol is slow the first time"

Expected. First-time learning takes 2-5 minutes (schema inference + exploration + canary). Subsequent runs are 10-20 seconds (replay).

If first-time is taking more than 5 minutes, the explore engine may have entered a retry loop. Check the trace — if you see 20 iterations and no convergence, the site is likely too complex.

Still stuck?

Email support@agas.ar with:

The execution_id (from the trace URL)

What you asked Sol

What you expected vs what happened

We read every support email. Response time: <24h business days.