Troubleshooting

Chronicle Won't Join Voice Channel

Symptoms: /start-session fails to connect to voice or Chronicle immediately disconnects.

Solutions:

• Make sure you're in a voice channel before using /start-session
• Check that Chronicle has Connect and Speak permissions for the channel
• If the voice channel has a user limit, ensure there's room for Chronicle
• Try running /start-session again — it will automatically reconnect

Recording Doesn't Start

Symptoms: /start-session runs but nothing seems to happen.

Solutions:

• Check that you have an active campaign (/campaign list)
• Verify Chronicle has the necessary permissions
• If you're within the cooldown window after a previous session, wait a few seconds

Empty or Short Recap

Symptoms: The recap after /end-session is missing information or very brief.

Solutions:

• Ensure the recording was at least a few minutes long
• Speak clearly — very quiet or overlapping audio can be harder to transcribe
• Check that your microphone is working properly in Discord
• Very short sessions (under 1 minute) may not produce detailed recaps

Commands Not Showing Up

Symptoms: You can't see Chronicle's slash commands in Discord.

Solutions:

• Wait a few minutes after installation — Discord can take up to an hour to sync slash commands
• Try restarting your Discord client
• Ensure Chronicle has Use Application Commands permission
• Check that you're looking in the correct server

Notion Integration Issues

Symptoms: /notion connect fails, or no Notion workspace appears as connected.

Solutions:

• Run /notion connect to re-authorize the Notion connection
• Ensure the Notion workspace has granted Chronicle access
• Use /notion status to confirm the current workspace and connection health
• If needed, run /notion disconnect and reconnect from scratch

Still Need Help?

If none of these solutions work:

• Visit our Support page for contact options
• Join our Discord support server for real-time help
• Email us with details about the issue, including any error messages