Hello everyone,

I’m currently working with Alma and Primo VE, and I’ve noticed something that I’m hoping others in the community might have experience with.

In our discovery interface, the item availability status does not always update immediately after a change is made in Alma. For example, when an item is checked in or its location is updated, the availability in Primo sometimes takes a while to reflect the change. This can occasionally lead to confusion for users who see an item listed as available or unavailable when the real status has already changed.

I’m trying to understand whether this delay is related to indexing schedules, caching behavior, or another configuration within the system. Ideally, we would like availability updates to appear as close to real time as possible so that patrons can rely on the accuracy of what they see in discovery.

Has anyone here successfully configured faster or near real-time availability updates between Alma and Primo VE? If so, what settings or approaches helped improve this? I’d really appreciate hearing how other libraries handle this situation.

Thanks in advance for any insights or suggestions! geometry dash meltdown