Troubleshooting

Browser fails to install

Beanscrape downloads Chromium via Playwright on first run. If this fails:

1. Check your internet connection.
2. Check firewall/proxy settings. Playwright downloads from Microsoft’s CDN.
3. Try running again. The download resumes where it left off.

Login fails

• Wrong credentials: Run beanscrape credential update <bank-id> to re-enter.
• 2FA timeout: If the 2FA prompt times out, re-run the scrape. Beanscrape waits for manual 2FA completion.
• Bank changed their login page: The script may need updating. Run beanscrape teach <bank-id> to recapture the login flow and regenerate the script.

No transactions returned

• Date range: Some scripts only fetch recent transactions. Check the script or run with --debug to see what date range is being queried.
• Account selection: If the bank has multiple accounts, the script may default to the first one. Check the script source.
• Page structure changed: Bank websites change frequently. The script may need updating.

Script errors

Run with --debug for detailed error output:

$ beanscrape run ./amex.csx --debug

Common issues:

• Selector not found: The bank’s HTML structure changed. Update the script.
• Timeout: The page took too long to load. Try running again; bank websites can be slow.

Browser state issues

Beanscrape saves browser session state (cookies, etc.) between runs. If you’re having persistent issues:

1. Clear browser state:

2. Delete the contents of this directory and re-run.

Getting help

• Community forum
• Email: [email protected]