As STATSCORE, we guarantee 99.5% uptime of our services, but sometimes Sometimes there are situations beyond our control that may affect Scoutsfeed customers. One example of such a situation is when the data feed stops unexpectedly.
...
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:
...
to “no” the game will be automatically unbooked and in the AMQP data feed you will receive information as follows:
| Note |
|---|
{"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 from that game after this message.
| Info |
|---|
Please note there is always possibility when the connection between ScoutsFeed server and customers 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 event_keep_alive message. |