Realm Trigger is Repeatedly Suspended

I have a trigger set up to fire on insert into the collection. Out of nowhere, everytime I insert into the collection, all of my triggers go into the suspended state.
The error message appears for every trigger I have enabled:
(ChangeStreamHistoryLost) Resume of change stream was not possible, as the resume point may no longer be in the oplog.
I restarted the triggers and reinserted the data. I also paused and resumed my cluster but still it happens every time now. How can I fix this?


Did you try to restart it with unchecking restarting with the resume_token? Just note that if you do not use a resume token, the trigger begins listening for new events but will not fire for any events that occurred while it was suspended.

1 Like