Hi ! I use a

sensor

to detect files with high

minimum_interval_seconds

parameter (e.g. 12 hours) because the associated job performs many expensive queries on a database. In my daily use, I would like to be able to trigger the sensor tick manually (without having to wait 11 hours in the worst case) if I notice that an important file has been dropped. Is there a way to meet this need? I also wonder if it is possible to get the cursor of a sensor inside an op/asset to update it.

We currently don’t have that supported in the UI. But we’re planning on adding something similar for testing. would you expect to kick off the manual run when the sensor is off so that the manual ones don’t fight with the one that’s running on the daemon?