Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to

Radix IoT Website Mango 3 Documentation Website Mango 4 Documentation Website

  • Hi,

    what does this mean:

    Points: 310, sent 310 requests, synced 249 records, target overcounts: 26, response errors: 0, elapsed time: 15.4s

    And what is the solution to the problem if it is one?

  • Hi Ralf,

    It means that for 26 points there was more data already on the receiving end than data on the publisher's side for the period checked. Usually this is caused by a point with interval logging on the publisher transmitting its realtime updates as opposed to logged events, then the receiver's default point logs all data if the receiver is configured to save real time data, and that amounts to an overcount. It can be possible other ways (disk getting full, importing extra data at receiver, etc), but that's what I'd guess caused it here. The solution to prevent it if that is the cause would be to change your publisher's publish event to logged data instead of updates.