I think this is an incorrect assessment. I’ve done more testing and this issue does not seem to be related to global vs. local deployment like I first thought.
To summarize my setup:
I have a Github repo/Github Actions that automatically deploy a Realm app based on push/pull request.
On push, the Realm app is automatically pushed to a “DEV” environment (which is a separate Atlas project), and integration tests are run immediately after deployment, which include testing trigger functionality. So far, the triggers have been working as expected in DEV.
On pull request, the exact SAME codebase is deployed to a “TEST” environment (which is another Atlas project) and the SAME integration tests are run, which currently fail consistently every time on the trigger tests.
What I’ve noticed is the trigger doesn’t seem to “initialize” for at least 10-15 minutes after deployment in the TEST environment, so when the integration tests run immediately after deployment, the trigger is not yet running (I can confirm in the UI (“Last Cluster Time Processed” shows blank). If I wait (don’t have to re-deploy either like I initially thought), the trigger does eventually start.
But now I’m wondering why there is a delay with the trigger in TEST project vs. DEV.