Southwell 18:30 suspended from 18:29:17 as part of site-wide issue.
Bet Angel history shows the race was unsuspended and went into play as normal at 18:30:47 and was suspended at the finish at 18:31:11, but in actual fact the market was suspended throughout.
Today's Horse Racing
- jamesedwards
- Posts: 6300
- Joined: Wed Nov 21, 2018 6:16 pm
- jamesedwards
- Posts: 6300
- Joined: Wed Nov 21, 2018 6:16 pm
Racing markets seem to be fully operational again. All races between 18:05 and 18:50 were disrupted.
I thought I was going mad but the Win market looked this this on my ladder, and only that market all else was fine, including the Place. Every runner was missing a name and had a number instead
I do some runner name retrieval via the API just pre-off, and as none of the names matched it completely threw my automation on that race
You do not have the required permissions to view the files attached to this post.
Looks like a selectionID as you're probably awaresniffer66 wrote: ↑Tue Oct 06, 2026 8:51 amI thought I was going mad but the Win market looked this this on my ladder, and only that market all else was fine, including the Place. Every runner was missing a name and had a number instead
I do some runner name retrieval via the API just pre-off, and as none of the names matched it completely threw my automation on that race
Were you able to rule out a visual bug from your BA version?
For example do you call listMarketCatalogue/listRunnerDescription outside the BA environment or inside? ...and found that runnerName was = selectionId? Perhaps the former was failing for some reason on that particular marketID and a BA error handler just fetched the selectionID as a backup. Ultimately we do see odd selection names from time to time so there seems to be some human input but presumably they have checks and balances and a whole UK horse race would be easily flagged and fixed upon market creation. Could well be front end issue as historically runnerName and selectionId are identical across the place/win markets so if all was good in Place it could be your BA instance, especially if your API runner retrieval is simply exporting what your BA instance was holding for the value
