FormGenie Bot Status Messages
What do the various Red Status reports mean?
| Status Report | Meaning |
|
No races match your criteria |
Unless you have selected 'Auto-Load' at start up, this can happen if you have tried to load the races without closing the bot down first and clearing the previously loaded races. Simply logout, close down and restart the bot. |
|
Race Omitted: No Places |
There are no place backs available that satisfy the set Place parameters set in row 6. |
| Race Omitted: X Previous Races not Settled |
Awaiting confirmation of the official result. Could be delayed by photo finish or stewards enquiry. User has the option to use Provisional Results (row 10) to allow the bot to play the next race without waiting for the official result. If an abandonment happens during racing and you don't have 'Use Provisional Results' ticked, the Bot will not place any more bets as it thinks it needs to wait for the latest result. The only solution is to close down and restart. |
|
Race Omitted: A Runner(s) < Min Back Price of X |
A Top rated selection does not meet the minimum odds requirement set in 6. |
|
Race Omitted: Dutch Selection(s) < Min Dutch Price of X |
A Dutch/Top selection does not meet the minimum odds requirement set in row 10. |
|
Race Omitted: Coupled Price: X <= Default MinCoupled Price: Y |
The current Coupled Odds of the shortest 2 selections is below the value set in row 10. |
| Race Omitted: Current Coupled Price: X <= Current MinCoupled Price: Y | The current Coupled Odds of the shortest 2 selections is below the value set in row 10, but is adjusted by the 'DynamicMin Coupled price in row 10. |
|
Race Omitted: Coupled Price: X > MaxCoupled Price: Y |
The current Coupled Odds of the shortest 2 selections is higher the value set in row 10. |
|
Stopped at Winner |
The bot stopped at the first winner as set in row 2. |
|
Stopped: Winner at X Races from End of Card |
The bot has stopped at a given race count from the end of the loaded races. |
|
Stopped: Day Profit 'xx' > 'xx' |
The bot has reached the profit as set in row 2. |
|
Stopped: Session Loss > 'xx' |
The bot has reached the Loss as set in row 2 |
| RunnerName] [lastMatchedPrice] < [dutchMinPrice] | The last matched price is less than the Min Dutch price as set in row 10 |
| RunnerName] [lastMatchedPrice] < backMinPrice] | The last matched price is less than the Min Back (Top rated) price as set in row 10 |
|
Race Omitted: Market Inactive |
The race may have been void/abandoned and the bot is awaiting confirmation of the official result. The result could be delayed by photo finish or stewards enquiry. User has the option to use Provisional Results (row 10) to allow the bot to play the next race without waiting for the official result. If an abandonment happens during racing and you don't have 'Use Provisional Results' ticked, the Bot will not place any more bets as it thinks it needs to wait for the latest result. The only solution is to close down and restart. |
|
Race Omitted: An Eq Dutch Stake would need to be reduced by > 75% |
The Bot has an in-built maximum Stakes Reduction of 75%. This means the Bot is governed by the Max Liability stake, but will only place the bet/s if the stake does not have to be reduced by more than 75% to return a profit. This is basically because the Bot can't reach 100% of the recovery amount based on your Max Stake. So it looks to recover the minimum. However, it will not attempt to recover more than the default target if the Max Stake has to be reduced by more 75%. This is to avoid huge stakes for a disproportionate return. |
|
Stopped: Total Win Probability [totalWinProbability] > 1 |
The combined odds of the selections are too short to return a profit |
| Stopped: A Dutch Stake was > XXX | The Dutch Stake required to return the target amount exceeds your Max Stake. So the Bot voided the race. |
|
Race Omitted: Coupled Price: -1.0 = or less than Default Min Coupled Price of XX. |
The Bot has lost connection to Betfair servers and cannot calculate the min coupled odds value so is returning -1. Confirm BF status update. If OK then it's your wifi connection that has dropped out. (MACs are bad for this. Consider using a VPS). |
|
Race Omitted: Failed to get Market for 600 secs |
1. There is a connection issue from your machine to Betfair. It maybe a local issue or a Betfair issue. You can Check Betfair's API status here. Since your races are already loaded into the Bot this error message has nothing to do with our servers. If you get this message you will have to logout and restart the bot (though this may not fix the underlying cause). Any bets scheduled may have already been submitted and you should be able to see these on the loaded race tabs. Anything still waiting to be submitted will not have been. In this instance you should login to your Betfair account and see what has been matched/unmatched. 2. This can happen if you are using a Laptop/MAC and it's gone into Power Save or Hibernation. It is therefore advisable to switch off any such features. If this issue persists it could be the case that your internet connection drops out when there is no internet activity i.e between races (this particular problem is more common with MACs using Wifi - search Google for more info). You could try running a browser in the background connected to a constant stream something like sky news or a radio station to keep the connection alive. Or you can try having a 2nd instance of the bot running profile #13. This simply monitors the markets and is constantly polling Betfair. If you continue to have problems, you may need to use a hardwire to your router, use a PC or use a VPS service. |
|
Max dutch selections reduced to two |
This is because The LINK MIN COUPLED PRICE is ticked: This works by linking the 'MinCoupled Odds' the bot will accept to the size of the current target. So if the 3rd horse's odds are too short then the Bot will only place stakes on the other 2 selections. |
|
Race Omitted: < [minRunners] Runners |
There are too few runners in this race to satisfy the setting in row 4. |
| MaxDutches reduced to lowest odds. MinCoupled linked to Target | If the combined odds of the shortest priced horse's odds are relatively short when linked to the next recovery target, then the Bot will exclude the 3rd/4th selections and only place stakes on the 2 shortest priced selections. This keeps stakes lower. It's optional and whilst you may find an excluded selection wins on occasion, its' use is advisable. The calculation is: MinCoupled Odds must be =< Current Target X 0.5%, else only 2 qualifiers are backed. This figure has a ceiling of 4.0, so if the Min Coupled Odds >4.0 all Top/Dutch qualifiers will be included. |
| BOT HAS STOPPED RUNNING; No valid Authorisation Token found. | This is either because your Authorisation Token has expired or there was a drop in your internet connection at a time when the bot periodically polls our severs for validation. Once it cannot validate, the Bot will need restarting to resume. If you still have this error following a restart and you have internet connection then please contact support. |
What does 'Unable to reach market for 600 seconds' message mean?
1. Although very rare, this means the connection between your bot (not our servers) and Betfair has disconnected. It could be an issue local to you (dropped internet connection etc) or Betfair's own servers.
1a) You can check by seeing if you can login directly to Betfair (via a web browser).
1b) BF use diferent servers for the Bot API so you may also need to check Betfair's API status here.
Since your races are already loaded into the Bot this error message has nothing to do with FormGenie servers. If you get this message you will have to logout and restart the bot (though this may not fix the underlying cause). Any bets scheduled may have already been submitted and you should be able to see these on the loaded race tabs. Anything still waiting to be submitted will not have been. In this instance you should login to your Betfair account and see what has been matched/unmatched.
2. This can happen if you are using a Laptop and it's gone into Power Save or Hibernation. It's therefore advisable to switch off any such features. If this issue persists it could be the case that your intent connection drops out when there is no internet activity i.e between races. You could try running a browser in the background connected to something like sky news or a radio station to keep the connecting alive. Or you can try having a 2nd instance of the bot running profile #13. This simply monitors the markets and is constantly polling Betfair.
What happens if there are NonRunners?
The bot will substitute selections that become NonRunners by promoting the next ranked horse as long as the FormGenie Dutch 'runners to selections' ratio is still satisfied. However, the bot will only do this if the Min Stars parameter (Row 6) is set to zero. When a substitute is used it will be highlighted in orange. If the original Top Rated is a non runner, the next ranked will be promoted to Top. An up-arrow in the blue cell will indicate this has occurred. Rest assured there is a strong correlation between the FormGenie ratings rank and winners - so promoting them is perfectly logical.
What do the P&L Figures tell me?
This graphic should explain:
£36.06 is the profit since the bot was started (so could be several days or just 1 race ago).
£84.57 is the profit today including any carried over losses from yesterday.
£73.21 is the loss carried forward from yesterday (or the last time the bot was restarted).
£11.46 is the profit from today excluding any carried-forward losses that may now been recovered. This is the day-profit and therefore the StopProfit fig the bot will work to today.
Live trial
Access the live trial now
Live Trial
Buy Now
Now offering day passes
Buy Now
FormGenie Bot
Automated Betfair Betting
Buy Now