LibertyTools / Docs
Troubleshooting
Start by finding the last place your event appeared. That tells you whether to check ER:LC setup, your LibertyTools output, or the application receiving the event.
No incoming events
- Open your connection's Events tab and refresh. A
WebhookProbeis a connection check; aCustomCommandevent means the in-game command reached LibertyTools. - If nothing appears, check that the connection's ER:LC webhook URL is saved on the same private server you are testing.
- Check whether the connection is paused in Settings. A pause rejects new events.
- Try one real in-game custom command, then look for it in Events. If it still does not appear, contact LibertyTools support with the time, event type, and connection name. Do not send keys or tokens.
The event arrived, but the hosted command did not reply
- Open Commands and confirm the rule is published, not just saved as a draft.
- Confirm the command name matches the in-game command.
helpand;helprefer to the same rule. - In Settings, confirm the server key is connected and the server owner authorized LibertyTools.
- Read Recent command runs. It shows success, failure, Command waiting, or a safety stop for that action.
Command waiting means the action has not been sent yet and retries automatically when capacity is available. Do not repeat it just because it is waiting. Unsent work expires after five minutes. Rejected or uncertain requests are not automatically replayed; read the result before trying again.
A private reply cannot reach a player who has already left the game. Avoid using private replies as a replacement for normal Roblox chat.
The Poll bot is running but sees nothing
- If Events has no incoming event, fix the webhook setup first.
- In Outputs, check that your Poll client exists and note its pending and dropped counts.
- Confirm the running bot has that client's subscription ID and private token. A public webhook URL or old webhook ID is not a substitute for the v2 Poll token.
- Check the bot's
pollErrorlogs. For429, wait for the retry period. For credential errors, check that the subscription ID and token match; rotate an exposed or lost token. A paused or restricted connection can return 404; check its dashboard status.
If the bot was offline for over 14 days or its backlog exceeded 5,000, older events may have been dropped. The dashboard shows that count.
Forwarding is delayed or paused
- Open Events → Forwarding deliveries to see the latest response and retry attempts.
- Check that your endpoint is reachable and returns a quick
2xxafter it safely accepts an event. - Check the destination's health in Outputs. A new destination remains in probation until a successful response.
- After fixing a paused handler, click Retry forwarding. For Signed Proxy, this sends a test event. For Exact ER:LC copy, enable connection checks in Edit and save the LibertyTools webhook URL again in ER:LC to trigger a genuine signed check. An active Signed Proxy handler can be tested using More → Send test event. See the forwarding guide for the full setup.
A slow or failing destination should not stop Poll or healthy destinations. Its queue is bounded, so check the dashboard for skipped or lost work after a long outage.