MongoDB Atlas Trigger Scheduled erroring when Cluster is Paused

MongoDB Atlas App Services & Realm Atlas Triggers & Functions
#1

We have a simple test Trigger script that runs and errors when the our cluster is PAUSED.

exports = function () {
  console.log('STARTED');
  const db = context.services.get('my-cluster').db('database');
  const connections = db.collection('connections');
  connections.findOne(); // THIS ERRORS WITH TIMEOUT IF CLUSTER IS PAUSED
  console.log('FINISHED');
};

Within this function execution is there a way to check if the cluster is PAUSED?

Alternatively we could Disable/Enable triggers when we Pause/Resume?

Thoughts?