Ask Your Question

Revision history [back]

VA CAAR - Missing some photo updates

Login URL: http://caar.rets.paragonrels.com/rets/fnisrets.aspx/CAAR/login

Account name: BLUEROOF360

I'm pretty sure this is on my end, I just need help trying to figure out why. We occasionally miss photos for new listings and I can't figure out why. The only pattern I've noticed is that in most cases, the photos seem to show up before the listing does (i.e. L_InputDate > L_Last_Photo_Updt), but I don't think that matters.

Using VA CAAR as an example (but I doubt this problem is specific to this feed). We query for photo updates using the Media resource. A query for the last hour of updates looks like this:

(L_Last_Photo_updt=2019-03-08T17:50:19+00:00-2019-03-08T18:50:24+00:00)

We use this to identify which listings changed, then we do another query to get all of the URLs for each listing affected (replacing all URLs for a listing like this ensures deleted photos get removed too).

Our incremental downloads pick the next min date by saving the max update date of the results of this download.

Does anything about this sound wrong? Do we need to do any "overlapping" in our date range downloads (like if there's any sort of replication lag, for example)? I'm at a loss...

Thanks much for your time!

VA CAAR - Missing some photo updates

Login URL: http://caar.rets.paragonrels.com/rets/fnisrets.aspx/CAAR/login

Account name: BLUEROOF360

I'm pretty sure this is on my end, I just need help trying to figure out why. We occasionally miss photos for new listings and I can't figure out why. The only pattern I've noticed is that in most cases, the photos seem to show up before the listing does (i.e. L_InputDate > L_Last_Photo_Updt), but I don't think that matters.

Using VA CAAR as an example (but I doubt this problem is specific to this feed). We query for photo updates using the Media resource. A query for the last hour of updates looks like this:

(L_Last_Photo_updt=2019-03-08T17:50:19+00:00-2019-03-08T18:50:24+00:00)

We use this to identify which listings changed, then we do another query to get all of the URLs for each listing affected (replacing all URLs for a listing like this ensures deleted photos get removed too).

Our incremental downloads pick the next min date by saving the max update date of the results of this download.

Does anything about this sound wrong? Do we need to do any "overlapping" in our date range downloads (like if there's any sort of replication lag, for example)? I'm at a loss...

Thanks much for your time!

Edit: In case this is useful, here are a couple displayIds we missed photos for, but got the listing just fine:

586742 586853

Note that this doesn't affect all new listings, just some.

VA CAAR - Missing some photo updates

Login URL: http://caar.rets.paragonrels.com/rets/fnisrets.aspx/CAAR/login

Account name: BLUEROOF360

I'm pretty sure this is on my end, I just need help trying to figure out why. We occasionally miss photos for new listings and I can't figure out why. The only pattern I've noticed is that in most cases, the photos seem to show up before the listing does (i.e. L_InputDate > L_Last_Photo_Updt), but I don't think that matters.

Using VA CAAR as an example (but I doubt this problem is specific to this feed). We query for photo updates using the Media resource. A query for the last hour of updates looks like this:

(L_Last_Photo_updt=2019-03-08T17:50:19+00:00-2019-03-08T18:50:24+00:00)

We use this to identify which listings changed, then we do another query to get all of the URLs for each listing affected (replacing all URLs for a listing like this ensures deleted photos get removed too).

Our incremental downloads pick the next min date by saving the max update date of the results of this download.

Does anything about this sound wrong? Do we need to do any "overlapping" in our date range downloads (like if there's any sort of replication lag, for example)? I'm at a loss...

Thanks much for your time!

Edit: In case this is useful, here are a couple displayIds we missed photos for, but got the listing just fine:

586742 586742

586853

Note that this doesn't affect all new listings, just some.