#enable deeper debug

1 messages · Page 1 of 1 (latest)

short ironBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

ocean wagonBOT
#

Yes! Here are a few ways to get more visibility:

1. Check the session logs for that specific sessionId:

clawdbot sessions history 3852107e-541b-440e-893b-6a917bc5341d

Or using the session-logs skill: qmd search "3852107e" in your session logs.

2. Enable debug logging:

clawdbot gateway call config.get  # see current logging config
clawdbot gateway call config.apply --raw '{"logging.level":"debug"}'

Then restart or it should pick up the config change.

3. Check gateway logs directly:

# 
clawdbot gateway logs --tail 100
# or for specific runId
clawdbot gateway logs | grep f17e9679

4. The session-logs skill can search your conversation history:

# First index your session logs
qmd index ~/clawd/.sessions/
# Then search
qmd search "The AI service returned an error"

The session-logs skill (in /opt/clawdbot/skills/session-logs/SKILL.md) has good examples for querying past runs by session ID or run ID.

For the specific error you're seeing, it looks like the qwen-portal provider is failing. Check your model provider configuration and make sure your Qwen API key is valid and you have quota remaining.

#

Try these commands directly:

# See session history for that specific session
clawdbot sessions history 3852107e-541b-440e-893b-6a917bc5341d

# Or search all session logs for that runId
qmd search "f17e9679"

# Check gateway logs in real-time
clawdbot gateway logs --tail

If clawdbot isn't in your PATH, you may need to run it via bun/pnpm:

bun clawdbot sessions history 3852107e-541b-440e-893b-6a917bc5341d