Reason of interruption | Data feed information |
---|
The scout's temporary technical problems | Added “Technical problem” problems” incident (ID:1200) as soon as possible Changed the “betstatus” to “suspended” After restoring the continuity of the data feed, needed correction will be done, the relation will be continued and betstatus will be changed to “active” value If it is not possible to continue the relation - Changed the “scoutsfeed” parameter to “no” which is equivalent to the cessation of data delivery
|
The Scout lost the transmission source | Added “Technical problem” problems” incident (ID:1200) by Scout Quality Controllers (SQC) as soon as possible Changed the “betstatus” to “suspended” After restoring the continuity of the data feed, needed correction will be done, the relation will be continued and betstatus will be changed to “active” value If it is not possible to continue the relation - Changed the “scoutsfeed” parameter to “no” which is equivalent to the cessation of data delivery
|
The Scout lost the internet connection | Added “Technical problem” problems” incident (ID:1200) by Scout Quality Controllers (SQC) as soon as possible Changed the “betstatus” to “suspended” After 30 seconds we will stop sending "event_keep_alive" messages After restoring the continuity of the data feed, needed correction will be done, the relation will be continued and betstatus will be changed to “active” value If it is not possible to continue the relation - Changed the “scoutsfeed” parameter to “no” which is equivalent to the cessation of data delivery
|