This can be caused by some of the event messages being lost on the way from mod-feesfines to mod-patron-blocks through pub-sub/Kafka, so the data is out of sync. We have a synchronization mechanism that can be a temporary workaround in such cases. We have a synchronization mechanism that can be a temporary workaround in such cases. You can re-sync automated patron blocks data for a single patron like this: POST /automated-patron-blocks/synchronization/job body: { "scope": "user", "userId": "{USER_ID}" } or you can do a full re-sync for all patrons (this can take a lot of time depending on the amount of loans, fees/fines and other data): POST /automated-patron-blocks/synchronization/job body: { "scope": "full" } These calls return a sync job object with an ID, you can use this ID to monitor its status, number of processed objects, errors etc.: GET /automated-patron-blocks/synchronization/job/{SYNC_JOB_ID}