As STATSCORE, we guarantee 99.5% uptime of our services, but sometimes there are situations beyond our control that may affect Scoutsfeed customers. One such situation is when the data feed stops unexpectedly.
Main reasons for interrupted data feed delivery:
technical problems of the scout
loss of transmission source (for TV coverage)
loss of internet connection (mainly for relations from the venue coverage)
other reasons
Depending on how you receive data, you may be notified in different ways when the data feed has been interrupted:
Reason of interruption | Data feed information |
---|---|
The scout's temporary technical problems |
|
The Scout lost the transmission source |
|
The Scout lost the internet connection |
|
Change of the “scoutsfeed” parameter from “yes” to “no” for live events
After the “scoutsfeed” parameter is changed, depending on how the data is received, the recipient will be informed of the cessation of data delivery as follows:
API data feed
Information received after changed the “scoutsfeed” parameter:"error": {"message": "You have not booked this event/resource","status": 403,"internal_code": 16}
AMQP data feed
Information received after changed the “scoutsfeed” parameter:
Received {"id":414928815,"uuid":null,"type":"event","source":147640,"ut":1608201728,"data":{"event":{"id":2750161,"action":"update","start_date":"1900-01-01 09:46","ft_only":"no","coverage_type":"from_tv","status_id":1,"sport_id":5,"day":null,"neutral_venue":"yes","item_status":"active","clock_time":null,"clock_status":null,"area_id":208,"competition_id":1004,"season_id":26769,"stage_id":0,"group_id":null,"tour_id":null,"gender":"male","bet_status":"suspended","bet_cards":"suspended","bet_corners":"suspended","relation_status":"finished","status_type":"scheduled","name":"Test 1 - Test 2","round_id":null,"round_name":null,"scoutsfeed":"no", (..)
You will no longer receive any further messages after this message.
There is always possibility when the connection between ScoutsFeed server and customer receiver end-point is broken or the data transmission is delayed. To determine such cases we suggest to handle special message type: “event_keep_alive”. See more about /wiki/spaces/SCOUT/pages/1805778945 message.