BF Bot Manager Troubleshooting: Why Your Bot Is Not Betting (2026)

Troubleshooting Checklist (In Order)

When BF Bot Manager loads but never bets, work through these steps before changing your strategy logic. Jumping straight to rule edits often hides a simpler infrastructure problem.

1. Check markets

• Are markets visible in the Markets tab?
• Did Auto Load filters exclude your event? Wrong sport, time window too narrow, or min liquidity too high are the usual culprits — see Auto Load guide.
• Is the market suspended or closed? In-play suspensions are normal; the bot waits.
• Did the meeting start without loading? Enable auto-load new markets and check VPS uptime if running remotely — VPS guide.

Quick test: Manually load one market you expect the bot to trade. If it still does not fire, the issue is strategy rules — not Auto Load.

2. Check Strategy Reports

Strategy Reports show which Bet Rules passed or failed on each refresh cycle. This is the most underused debugging tool in BFBM.

• If entry conditions never turn green, the bot correctly waits — widen odds bands, relax time windows, or fix score filters.
• If conditions turn green but no bet appears, move to steps 3–4 (assignment, bet process).
• Export or screenshot reports when asking Ask Bob — it helps pinpoint rule logic.

3. Check strategy rules and assignment

• Is the strategy assigned to the loaded market (or global assignment enabled)?
• Is the strategy paused or stopped? Check the toolbar status.
• Conflicting AND/OR logic — e.g. “odds > 3.0 AND odds < 2.5” blocks all entries.
• Daily P&L limit or max bets already hit — bot stops until reset or next day.
• Unsettled markets rule — with recovery staking, bot waits for previous bet to settle; this looks like “not betting” between races.
• Simulation vs Real — confirm which mode is active; icon should match your intent.

4. Check bet process and exchange response

• Sufficient Betfair balance in Real mode (Simulation ignores balance).
• Minimum stake / tick size — sub-£2 stakes often fail on some markets.
• Liability vs stake — lay bets need affordable liability; check lay liability calculator.
• Betfair error messages in bet log — API outage, market suspended, bet blocked.
• Check status.betfair.com during outages.

5. API connection limit

Betfair allows two simultaneous API connections per account. If bets stall with connection errors:

• Close Geeks Toy, Bet Angel, Traderline API mode, or a second BFBM window.
• On a VPS, ensure only one scheduled task launches BFBM.
• Log out and back into BFBM to refresh the session after closing other apps.

Symptom → Likely Cause

After Bet Rule Issues (Position Stuck Open)

If the bot places entries but never closes:

• Confirm After Bet Rules exist and are linked to the entry rule set.
• Green-up target may be unreachable — price never reaches profit threshold before time exit.
• Add a hard time exit — stop-loss guide.
• In-play football: suspension may block exit until play resumes — normal behaviour.

Import / Clone Problems

Imported strategies from forums or XML packs may reference old market types or staking plans incompatible with your account:

• Re-select exchange and market type after import.
• Re-link Auto Load template to your filters.
• Run imported strategies in Simulation only until validated.

When to Reset vs When to Tune

• Reset strategy assignment if you cloned markets manually and assignments broke.
• Tune rules only after Strategy Reports prove conditions never match.
• Do not enable recovery staking to “fix” losses — fix entry edge first.

Connection and Login Issues

• Expired Betfair session — re-enter password or refresh SSO in BFBM settings.
• Wrong exchange selected — strategy imported from Betfair but Matchbook markets loaded (or vice versa).
• Firewall on VPS — outbound HTTPS blocked; bot loads markets but cannot place bets.
• Clock skew — VPS time wrong by minutes; time-before-off rules never fire. Sync NTP on the server.

Prevention Habits

1. Follow first bot 10-step workflow for every new strategy.
2. Name strategies with version numbers (_v2) so rollbacks are easy.
3. Set safety caps before first Run click.
4. Keep one logbook column: “expected bets” vs “actual bets” per session.

Need step-by-step setup? Start with your first bot in 10 steps, browse the BFBM hub, or ask Ask Bob a specific settings question.