Today we experienced something weird. We have a publication on a certain collection. It is a dynamic publication, users call the publication function with a parameter. That parameter is the same for a group of users, so at the same time a group of logged in users will probable share the same publication cursor.
After one user deleted a document from the collection, the document was not removed from the publication and remained visible for the all users. Checking the database remotely however showed that the document really had been deleted from the database.
I checked the application several times in the next two hours, using different users logging in and out, but the deleted document remained visible, also for new users logging in.
Then after three hours, the document suddenly disappeared from the publication.
I don’t understand in first why the publication did not update immediately. How is the publication triggered to rerun the query and what could possibly caused it not doing this? Any ideas?
I tried the same workflow on a copy of the application running on another galaxy container looking at another database instance and things worked wel there. The publication updated immediately after removal of the document.