Troubleshooting

Use this guide when something does not behave as expected.

I do not see Mahout in the dashboard

Your account probably does not have the Mahout permission yet. Mahout requires its own product permission, enabled per account. If you believe you should have access, contact support@airavat.xyz.

A data source is unavailable

A source can be temporarily down, return incomplete data, or be outside what your request needs. Mahout should explain the missing source and continue with the sources it can use.

If a specific source matters to your analysis, ask:

Which sources were unavailable for that answer, and can you retry the missing one?

The response stopped or never finished

Try:

1. Wait a few seconds for the terminal status.
2. Refresh the page.
3. Reopen the same session from history.
4. Retry with a shorter prompt or lower effort.

If the problem repeats, contact support with the session, time, and prompt.

I was logged out during a long session

Dashboard sessions end after about two hours of inactivity. Active use extends the session automatically — you are only ever logged out after two quiet hours, never while you are working. If Mahout stops responding or the dashboard asks you to sign in, reload the Airavat dashboard, sign in again, and reopen your session from the History tab.

A sandbox or backtest failed

Sandbox-backed work can fail because of data availability, generated-code errors, provider downtime, or limits.

Try:

• ask Mahout to explain the failure
• simplify the rule or time range
• rerun the artifact
• use a smaller data window
• ask for a non-code summary instead

An artifact will not save

The output may not be a supported artifact type, or the save request may have failed.

One known cause: the content-safety filter rejects real raw HTML in artifact content — for example a <script> tag or an <img src=...> element embedded in a report or chart title. Ordinary analysis prose is fine: comparison expressions like price<sma or rsi>70 and generics like List<string> are not flagged. If a save is rejected, remove the embedded HTML and try again.

Otherwise, try saving the final chart, table, note, or backtest output again. If the same artifact repeatedly fails, contact support.

An artifact will not rerun

If the artifact was built with a data source that has since been removed from Mahout, the rerun is refused with an ARTIFACT_SOURCE_REMOVED error. The saved artifact itself is kept; only the rerun is blocked. Rebuild the analysis in a new chat using currently available sources.

For other rerun failures, see the sandbox guidance above.

An agent will not deploy

When a draft agent fails to compile, Mahout explains the rejection. Common causes:

• the condition is ambiguous — reword it with concrete instruments, thresholds, and timeframes
• the rule uses a data source Mahout does not support for agents
• the rule asks for trade execution — agents only watch and notify

Reword the rule and deploy again. Previewing the agent against historical time before deployment is a good way to catch a rule that compiles but does not fire when you expect.

I am not getting agent notifications

Check that the agent is deployed and not paused. If it is active but quiet, ask Mahout to analyze its recent evaluations, or preview it against a historical window where you know the condition occurred to confirm the rule fires as intended.

The answer seems wrong or unsupported

Ask for source details before relying on it:

Show the sources, assumptions, and uncertainty in this answer.

What parts are facts and what parts are model interpretation?

What should I verify manually before using this?

Do not treat Mahout output as guaranteed truth or financial advice.

I hit a rate or usage limit

Wait and retry later. Higher-effort prompts, code-backed analysis, long streams, and repeated reruns use more resources than short chat responses.

I pasted something sensitive

Do not paste private keys, seed phrases, passwords, API keys, or sensitive personal information into Mahout.

If you accidentally pasted sensitive information, rotate or revoke it outside Airavat immediately.

Support checklist

When reporting an issue, include:

• approximate time
• dashboard account email
• session, artifact, or agent, if visible
• prompt or workflow
• expected behavior
• actual behavior
• whether it involved chat, an agent, the sandbox, or artifacts