Troubleshooting
Contents
Start here
- Check which EXE is running: use the latest package, not an old nearby release.
- Close duplicate ExtraExecutor instances. Do not begin by deleting account files.
- Record the exact error, preceding action, and time.
- For account issues, check vault unlock and account selection.
- For launches, open Launch & status → History for this app run.
Installation and interface
| Symptom | Cause / action |
|---|
| scripts/autoexec/workspace shortcut does not open | Old shortcuts may contain build-machine paths. Use release-shortcuts-fixed or newer and launch ExtraExecutor to refresh them. Direct path: %LOCALAPPDATA%\Potassium\folder-name |
| Missing DLL/bin | Extract the whole package; root ExtraExecutor.exe and bin/Potassium.exe are different components |
| Login page is 200×200 in a white window | WebView sizing was fixed on creation/navigation/resize/DPI changes. Close the old process and start the new build; replacing its EXE while it runs is insufficient |
| Unlock dialog clipped | Current dialog is compact and scrollable. Reduce excessive system scaling or enlarge the window; report DPI/size if unresolved |
| Add Account menu far from button | Position now comes from the button; opens above it if space below is insufficient |
| Saved @username stays visible | Success should clear after about 4 seconds; errors remain readable |
| Old original service operation has not been ported text | Old build/message. New builds implement some actions; remaining unavailable actions show a readable explanation |
| Wide table scrolls horizontally | RAM cap/Script added columns; enlarge or scroll. Data is not lost |
Login and vault
| Symptom | Action |
|---|
| Signed in on website but no account | Keep login window open until Saved; try Finish login and complete any challenge/2FA |
| Added account not visible | Set Folder to All accounts; adding resets filtering too. Check list-loading errors |
| Open the Roblox sign-in window first | Window is closed; reopen Manual Login |
| Roblox did not accept this session | Expired/revoked session; sign in again with the same account to update it |
| Could not contact Roblox / network failure | Check connectivity and Roblox access; retry later. Not necessarily an invalid password/cookie |
| Vault password rejected | Check keyboard layout and local password, not Roblox password. No automatic recovery |
| Vault fails on another PC | DPAPI is Windows-user-bound; encrypted file copies are not portable exports |
| Accounts exist but settings do not save | Inspect write errors/Retry save, disk space, folder permissions. Do not edit account-profiles.json as plain JSON |
| Recovery stops after closing Accounts | Closure locks vault and stops pending tasks; keep manager open |
Run, Attach, and scripts
| Symptom | Action |
|---|
| No client | Start Roblox, refresh, select intended client |
| Attach failed | Check bin helper/payload, client state, and exact error. Current Roblox compatibility is not guaranteed |
| Attached but Run has no effect | Check selected PID, Console, and actual runtime Luau support. GUI settings cannot fix missing execution bindings |
| submitted without results | Delivery is not execution; require output or real client behavior |
| File not submitted automatically | Check assignment, file existence, auto-attach, Send selected script after attach, successful attachment |
| Missing file after move | Reassign through Script |
| ExtraExecutor session bridge error | Enable signals, keep vault open, check target/auto-attach and compatible WebSocket runtime; wait for bridge with a timeout |
| Problems empty despite code errors | Native Luau diagnostics return an empty list; runtime/Console errors are separate |
Recovery and timers
| Symptom | Action |
|---|
| Signals switch was disabled | Current builds open Recovery when no target exists; without linked account/desktop it remains unavailable |
| Endless restarts | Check low memory cap, heartbeat timeout, repeated Schedule(0), recovery history. Stop recovery, fix cause, then re-enable |
| ScheduleFolder skipped account | Exact folder must be allowed by source; recipient needs linked account/target. Already live accounts are skipped |
| Need delay between accounts in one folder | ScheduleFolder lacks that individual queue. Separate folders can use different delays from request time; completion-based chains are in Workflow |
| Timer disappeared after restart | One-shot timers do not persist; script must resend after bridge readiness |
| No heartbeat | Check bridge execution and WebSocket.connect; send true is not native acceptance |
| Roblox error without recovery | Not every GUI error is recognized; cooperating scripts can call ReportDisconnected |
| Attempts exhausted | Fix cause from History, target/account/network; an explicit new launch starts a new scenario |
| cleaningCache blocks launch | Wait for completion/error; check other programs holding temporary files |
Clipboard, Quick Log In, and HTTP
- Clipboard is busy: focus ExtraExecutor, close the clipboard holder, retry.
- Select exactly one account: clear multi-selection and select one row.
- Player Link needs a numeric Place ID; optional Job ID is not a VIP URL.
- Quick Log In HTTP 400/404/410: obtain a new code; old one may be expired/used.
- HTTP 401: sign in again.
- HTTP 403: additional Roblox verification may be needed on the official site.
- HTTP 429: wait; repeated requests do not fix throttling.
- Copy Link produced text but no game: copying does not launch a URI; the registered Roblox protocol handler and ticket acceptance determine behavior.
Logs and bug reports
logs/wsstatus.log records socket startup; logs/wsevents.log records runtime event metadata in current Production code; logs/cberr.log records WebView creation failures; logs/panic.log records application panics. cberr may be absent without errors. Native crashes before the panic hook may produce no file. Older builds may contain raw runtime messages.
Logs/user output can contain private information. Send only relevant excerpts, removing cookies, tickets, tokens, VIP URLs, and personal data.
Include build folder/version, Windows/DPI, exact steps, expected/actual behavior, error, launcher/attach/script state, time, and history excerpt. “Does not work” alone cannot identify UI, persistence, launch, attachment, or runtime failure.