We have been tracking https://tea-can.dealertrend.com/providers/goxee/goxee_vehicleinventory_37803.csv for at least 2 months now. In recent history, the data provider seems to be sending a data file 0 times per day.
| reported | last modified | content length (bytes) | http status | hash |
|---|---|---|---|---|
| 462 (462 Bytes) | 404 | n/a | ||
| 137,202 (134 KB) | 200 | c9a7a58f25aabd7c0a4054f4a2928b968589ea8d | ||
| missing | ||||
| missing | ||||
| missing | ||||
| missing | ||||
| missing | ||||
| missing | ||||
| missing | ||||
| missing | ||||
| missing | ||||
| missing | ||||
| missing | ||||
| missing | ||||
| missing | ||||
| missing | ||||
| missing | ||||
| missing | ||||
| missing | ||||
| missing | ||||
| missing | ||||
| missing | ||||
| missing | ||||
| missing | ||||
| missing |
Good News!
We have determined that the size of this data feed looks like what we would consider 'normal'.
We do know that the resource itself says it was modified .
It is unknown when our data processors (what we call TEA-pot) made the last request for this resource.
But... since this feed has been configured for a while now, it's possible this resource isn't being processed directly by TEA-pot, but that it is an ancillary resource (it's not the only one being 'watched'), or that it needs further pre-processing before it can be used.
For example, if CSV column headers need to be added or remapped — this slows down the processing latency.