Troubleshooting
Solutions to common problems and error messages. If you don't find your issue here, visit our Support Server.
Common issues
Bot not responding to commands
Symptoms: You type a slash command but nothing happens, or commands don't appear in the slash command menu.
Solutions:
- Check bot status: Make sure Clocky shows as "Online" (green dot) in the member list
- Wait for Discord cache: After adding the bot, wait 1-5 minutes for commands to appear
- Check permissions: Verify Clocky has "Send Messages" and "Use Slash Commands" permissions
- Try in a different channel: Some channels may have permission overrides
- Rejoin the server: On mobile especially, leaving and rejoining can refresh commands
- Kick and re-invite: Remove Clocky and re-invite it
Commands not appearing in autocomplete
Symptoms: When you type /, Clocky's commands don't show up.
Solutions:
# Commands can take 1-5 minutes to appear after installation
# Be patient and try again in a few minutes
"Already checked in" error
Symptoms: You try to /checkin but get an error saying you're already checked in.
Cause: You can only be checked in to one server at a time.
Solution:
- Run
/statusto see which server you're checked in to - If it's a different server, go there and run
/checkout - Return to your desired server and run
/checkin
This is by design to ensure accurate time tracking. You cannot be checked in to multiple servers simultaneously.
Session auto-closed unexpectedly
Symptoms: Your session was automatically closed before you checked out.
Cause: Sessions auto-close after a configured period (default: 12 hours) to prevent inflated time tracking.
Solutions:
- Check auto-close setting: Ask an admin to run
/admin-set-autocloseto see or change the duration - Manual adjustment: If you were legitimately working, ask an admin to manually correct your session
- Best practice: Check out when you finish working, or use
/breakfor temporary pauses
Stats showing incorrect time
Symptoms: Your /stats display doesn't match your expectations.
Common causes:
- Break time excluded: Break time is NOT included in worked time (this is intentional)
- Different time range: Make sure you're viewing the correct range (today/week/month/all)
- Auto-closed sessions: Sessions closed by auto-close use check-in time + configured hours
- Timezone differences: All times are in UTC; display might differ from your local time
Verify:
/history limit:10
Review your recent sessions to see actual check-in/check-out times and durations.
Unable to export data
Symptoms: /data-export fails or no DM received.
Solutions:
- Enable DMs: Go to Privacy Settings β Allow direct messages from server members
- Check spam/requests: The message might be in your Message Requests folder
- Wait: Export processing can take 1-2 minutes for large datasets
- Cooldown: You can only export once every 24 hours
- Contact support: If still not working, join our support server
Error messages
"β You're not checked in"
When: You try /checkout or /break without being checked in first.
Solution: Run /checkin to start a session first.
"β οΈ User Limit Reached"
When: Server has reached maximum active users for its tier.
Current limits:
- Free: 5 users
- Premium: 100 users
- Pro/Lifetime: Unlimited
Solutions:
- Ask server admin to upgrade via dashboard.clockybot.com
- Wait for inactive users to be pruned (after data retention period)
- Ask admin to manually clean up old users
"π Permission Denied"
When: You try to use an admin command without "Manage Server" permission.
Solution: Only server administrators can use commands like:
/admin-close-session/admin-set-autoclose/admin-configure-deletion/admin-review-deletion-requests/rate-limit-stats
"β±οΈ Rate Limit Exceeded"
When: You've sent too many commands too quickly.
Current rate limits:
- Per-command cooldowns: 5-30 seconds
- Per-server limits: 60-300 commands/minute (tier-dependent)
Solution:
- Wait for the cooldown to expire (shown in error message)
- Consider upgrading for faster cooldowns (Premium: 50% faster)
- Admins bypass rate limits
"β Database Error"
When: There's a temporary issue with the database connection.
Solutions:
- Try again: Most database errors are temporary
- Wait a minute: Circuit breaker may be recovering
- Check status: Visit our status page (link in support server)
- Report if persistent: Join support server to report ongoing issues
Installation problems
Bot immediately leaves after being added
Cause: Server might be blacklisted or there's an automatic moderation bot kicking it.
Solutions:
- Check your server's moderation bot settings
- Whitelist Clocky in your anti-bot systems
- Ensure your server isn't on Discord's restricted list
- Contact support if issue persists
Missing permissions error
Symptom: Bot added but shows as offline or errors mention missing permissions.
Required permissions:
- Send Messages
- Embed Links
- Use Slash Commands
Solution:
- Go to Server Settings β Roles β Clocky
- Enable the permissions listed above
- Check channel-specific permission overrides
- Re-invite the bot if needed
Command issues
/checkin hangs or times out
Solutions:
- Check bot lag: Run
/statusto see if bot is responding - Database overload: Wait 30 seconds and try again
- Server outage: Check our status page
- Report if persistent: Join support server
/history shows no sessions
Possible causes:
- You haven't checked in/out yet
- Data retention period expired (Free: 1 year, Premium: 5 years, Pro: 10 years)
- You ran
/data-deletepreviously - Wrong server
Solution: Run /stats range:all-time to see if you have any recorded time.
/leaderboard is empty
Cause: Leaderboards are private by default. Users must opt-in.
Solution:
- Run
/publicto add yourself to the leaderboard - Ask other server members to opt-in as well
- Admins can check private stats with
/stats user:@username
Data & privacy
Can't delete my data
Symptom: /data-delete doesn't work or data still appears.
Check:
- Soft delete mode: Server might require admin approval
- Ask admin to run
/admin-review-deletion-requests
- Ask admin to run
- Confirmation required: You must click the confirmation button
- Other servers: Data in other servers requires separate deletion requests
Data export file is empty or incomplete
Solutions:
- Verify you've actually used the bot (run
/stats range:all-time) - Check that you opened the correct JSON file
- Data older than retention period is automatically deleted
- Re-run
/data-export(24-hour cooldown)
Concerned about privacy
Resources:
- Read our Privacy Policy
- Learn about GDPR Compliance
- See Data Export guide
- See Data Deletion guide
- Leaderboards are opt-in only (private by default)
Clocky does NOT have or request the "Message Content Intent" permission. Your messages are completely private and never read by the bot.
Still need help?
If your issue isn't resolved:
- Check FAQ: Visit our Frequently Asked Questions
- Review documentation: Search our docs for specific topics
- Join support server: Get live help from our team and community
- Contact us directly: Use the contact form on our website