Realm Trigger keeps being suspended, unclear why

I keep restarting a trigger and keep getting the same error:

this service was recently updated, so it may take several minutes 
until the cluster can be connected to. 
Error: error connecting to MongoDB service cluster: 
failed to ping: connection() : auth error: sasl 
conversation error: unable to authenticate using 
mechanism "SCRAM-SHA-1": (AtlasError) bad auth 
Authentication failed.

I have checked the data linked and it looks good. It seems like there might be something that goes wrong after I do a deploy from the CLI where I use the replace strategy.

Any ideas on how to debug this? Thanks!

Hi @Lukas_deConantseszn1,

Yea looks like cluster is not properly linked… I would suggest relinking the cluster. To see what caused first place I would recommend contacting support…


This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.