delay between add fave on Rails API, new fave showing up in node API about inaturalistapi HOT 2 CLOSED

I made it so the requests shouldn't get cached on the backend, and include no-cache headers. I'd be interested to see how that looks. There is usually a ~1second delay for data written to elasticsearch to be visible, and some of these operations may do that indexing in a delayed job. If it's still slow now, I can update those places to do indexing real-time and force ES to refresh with the new data.

from inaturalistapi.

I think we're good to go here. The API is setting no-cache headers for the details requests, and Varnish is properly not caching those requests. Rails is also refreshing the ES index after certain update methods, which ensures the updates are immediately available to the node API. If anyone notices even a small delay with details requests, please reopen this ticket with that info

from inaturalistapi.