Skip to main content
Committed ⭐️⭐️⭐️
ngupta26
Committed ⭐️⭐️⭐️
October 22, 2026
Question

Monitoring non-responsive subscriptions/triggers

Hi Cognite Team,

 

We have been using DM subscriptions for a while now and we know that it is very common for subscriptions to stop responding and we are forced to create new ones or start from a fresh cursor multiple times.

I have questions on how will this be monitored and responsibility for fixing it in case it doesn't work or stops responding and how do we find it. 

Can we have some alerts or emails sent to us incase if anything fails similar to for Extractors when it fails?

 

cc: ​@Neerajkumar Bhatewara 

      4 replies

      Arild Eide
      Expert ⭐️⭐️⭐️⭐️
      Arild Eide
      Expert ⭐️⭐️⭐️⭐️
      October 26, 2026

      Hi ​@ngupta26 

      Yes, Workflows has functionality for dispatching email notifications, as described in https://docs.cognite.com/cdf/data_workflows/workflow_user_guide#email-notifications. You can enable this by adding users to be notified in the UI for each Workflow.

      Is this what your are looking to troubleshoot as specific problem you are facing?

       

      Regards

       

      Arild Eide

       

      Committed ⭐️⭐️⭐️
      ngupta26Author
      Committed ⭐️⭐️⭐️
      October 27, 2026

      ​@Arild Eide thanks, but our requirement is if we can add a notification in cases when the workflow trigger is not responding. This is required because there were cases faced by the client where they added the data but the trigger didn’t run automatically. Then, they disabled the existing trigger and created a duplicate trigger which then started processing the data.

      Committed ⭐️⭐️⭐️
      ngupta26Author
      Committed ⭐️⭐️⭐️
      October 28, 2026

      @Arild Eide we only have an idea of steps that the client did. The trigger was deployed a couple of weeks ago and it ran properly for another day after the deployment. After that, there was data added in the system but the trigger reportedly stopped ingesting that data for few days. When the client noticed this, he disabled that trigger and created a new one with the same exact data modelling query and enabled it. Then it started ingesting data and continued to run. It continues to run fine till this day without any recent change/update. 

      So, we wanted to understand why would that happen and if there are any ways we can add notification for the same so it can be monitored more promptly if it happens again.

      Terms & ConditionsAccessibility statement