Skip to main content
All CollectionsRealm
App Services trigger keeps firing after being disabled
App Services trigger keeps firing after being disabled

Why does Atlas Trigger or Realm Trigger still fire after disabled?

Joao Boesso avatar
Written by Joao Boesso
Updated over a year ago

A trigger may keep firing temporarily after you disable it in App Services. This is because App Services can add the associated functions of a trigger to a queue and process them until there are no more events in the queue. App Services processes this queue even after you disable the trigger.

By reducing each trigger’s firing time, the time needed for the queue to clear also reduces. A trick to achieve this is to update the trigger’s associated functions as noop executions so that the functions can be completed more quickly.

Did this answer your question?