Ryven
Reference

Troubleshooting

Common issues and how to resolve them.

When something goes wrong, start here.


Ryven didn't respond in Slack

Symptoms: You mentioned @ryven but nothing happened — no thread reply, no task in the dashboard.

  1. Is the bot in the channel? Type /invite @ryven to add it.
  2. Is Slack connected? Check Settings > Integrations.
  3. Are you a workspace member? Only members can trigger tasks. Ask your admin for an invite.
  4. Did you use the right mention? The message must contain @ryven, not just the word "ryven".

Task stuck in "queued"

Symptoms: The task appears in the dashboard but stays in queued status.

  1. Is the Anthropic API key set? Check Settings > Integrations.
  2. Is the key valid? If revoked or expired, disconnect and reconnect with a fresh key.

Task failed during setup

Symptoms: Task moves to failed quickly, with an error about a setup command.

A command in your ryven.json setup.commands exited with a non-zero code. Check the agent output for details.

Common causes:

  • Missing lockfilenpm ci fails without package-lock.json. Use npm install instead.
  • Timeout — Default is 120 seconds. Increase setup.timeout in ryven.json.
  • Missing secrets — List required env vars in ryven.json secrets.

Task failed — sandbox timeout

Symptoms: Task ran for a long time and then failed with a timeout error.

The agent has a maximum execution time. Try:

  • Break it down — Split large tasks into smaller, focused instructions
  • Add a system prompt — Give the agent more context in ryven.json
  • Pre-build in setup — Move npm install / npm run build to setup.commands

CI keeps failing after retries

Symptoms: Ryven pushed fix commits but CI still fails, and the task moves to failed.

  1. Review the PR — The fix attempts may reveal what the agent was trying
  2. Check CI logs — The failure might be unrelated (flaky tests, infra issues)
  3. Fix manually — Fix remaining issues by hand, or close the PR and re-trigger with more specific instructions
  4. Improve the system prompt — Add guidance like "Always run pnpm typecheck before committing"

PR not opening

Symptoms: Task completed but no pull request was created.

The agent didn't make any code changes. Check the agent output to see what happened.

If you expected changes:

  • Be more specific in your task description
  • Include a GitHub issue URL for additional context
  • Check that the correct repository was selected

"Not a workspace member" error

Symptoms: You mentioned @ryven and got a reply saying you're not a member.

Ask a workspace owner or admin to invite you at Settings > Members, or approve your pending access request. Then link your Slack account in Settings > Profile > Linked Identities.


Still stuck?

Check the agent output in the task detail view — it contains the full log of what happened. Also review your ryven.json for configuration errors.

On this page