Sky API - delay after adding/updating constituents in the GUI

Max Szczurek

We noticed that if you add/update constituents in the web/database views in the RE NXT GUI, the changes don't propagate to the constituents API endpoint immediately - the endpoint is:

constituent/v1/constituents?last_modified=[Last modified date]

I recorded a video to demonstrate this and can share if necessary, but wanted to know if there's a straightforward explanation for this. We ran these steps to confirm the behavior:

1. Created a new record
2. Updated an existing record
3. Queried the API with a last_modified value of right before creating/updating these records; the changes were not reflected in the API call
4. Continued querying the API once per minute; after 7 minutes, the updated record was reflected; after 8 minutes, we saw both the new and updated records

I'm not seeing anything about a delay interval or a cache in a discussion or documentation - wondering if you can provide some insight into why there'd be a delay?

Alex Wong

@Max Szczurek
there is delay due to a Read Optimized Data Store is used for some data from constituent, gift, etc.

Max Szczurek

@Alex Wong
Thank you!