Troubleshooting

Common issues and how to resolve them

Quick Diagnostic Checklist

Is your agent in deployed status?
For Cloud agents: Is your Chrona Worker running?
Did the build complete successfully?
Are all required secrets configured in the Vault?
Is the endpoint enabled on the agent?

Build Errors

Build fails with "Module not found"

Cause

A required Python package is not listed in requirements.txt

Solution

Add the missing package to your requirements.txt file and rebuild the agent.

Build fails with syntax error

Cause

Invalid Python syntax in agent code

Solution

Check your code for syntax errors. The error message will include the line number.

Build times out

Cause

Large dependencies or slow network during package installation

Solution

Try removing unused dependencies. Contact support if the issue persists.

Deployment Issues

Agent stuck in "deploying" status

Cause

Deployment process is taking longer than expected

Solution

Wait a few minutes. If status doesn't change, try redeploying.

Cloud agent not connecting

Cause

Chrona Worker is not running or misconfigured

Solution

Ensure the Chrona Worker is running and properly configured with your API key.

"Worker not available" error

Cause

No worker is registered to handle this agent type

Solution

For Cloud agents: start your Chrona Worker. For Secure agents: redeploy.

Execution

Execution stuck in "pending" status

Cause

No available worker to process the task

Solution

Check that the agent is deployed and workers are healthy.

Task fails with timeout

Cause

Agent execution took longer than the configured timeout

Solution

Increase the timeout in endpoint settings or optimize your agent code.

Input validation error

Cause

Provided inputs don't match expected types or are missing required fields

Solution

Check that all required inputs are provided with correct types.

"Agent not found" error

Cause

The referenced agent/endpoint doesn't exist or isn't deployed

Solution

Verify the agent exists and is in "deployed" status.

Volt (Slack)

Slack user cannot message the bot

Cause

User is not a member of the ViksaAI project linked to the runtime

Solution

Add the user to the project in org settings. Their Slack email must match their ViksaAI account.

Credential validation fails

Cause

Missing bot scopes, Socket Mode app token, or incorrect signing secret

Solution

Regenerate the manifest from the Volt panel and recreate the Slack app, or add scopes shown in the validation report.

Runtime pod not running

Cause

Kubernetes deployment failed or was scaled to zero

Solution

Open Volt → Slack status. Resume the runtime or check cluster logs for volt-engine-service.

Authentication

Token refresh fails

Cause

Refresh token has expired or been invalidated

Solution

Log out and log back in to get new tokens.

SSO login fails

Cause

SSO configuration is incorrect or certificate has expired

Solution

Check SSO settings and verify IdP configuration matches.

"Unauthorized" error on API calls

Cause

Access token is expired or invalid

Solution

Ensure you're using a valid access token. Refresh if needed.

Still Need Help?

If you're unable to resolve your issue using this guide:

Contact support at [email protected]
Enterprise customers: Use your dedicated support channel
Slack / Volt issues: see Volt Slack setup