We have been tracking https://s3.amazonaws.com/sftp.dealertrend.com/users/dealerinspire/3152.csv for at least 5 months now. In recent history, the data provider seems to be sending a data file 1 time per day.
| reported | last modified | content length (bytes) | http status | hash |
|---|---|---|---|---|
| missing | ||||
| missing | ||||
| 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.