I am experiencing some problems with our sensor.

dagster._core.errors.DagsterUserCodeUnreachableError: dagster._core.errors.DagsterUserCodeUnreachableError: The sensor tick timed out due to taking longer than 60 seconds to execute the sensor function.

But we have a similar sensor that does the same but on a different dataset that is working fine. When running locally the sensor function completes fast enough. tried adding logs but those don’t appear.

We should do a better job of exposing those sensor logs back to you in Cloud - I’ll make sure my team is aware of it. I do see a log line internally that implies the sensor is finding a lot of S3 keys (I’ll DM you the specifics) - this might be an issue where it’s struggling to finish in time the first time it runs? And chunking the work further so it only ever processes n keys and then moves onto the next tick might get this working again.

I'm experiencing the same issue with a sensor I have deployed that reads files from S3

At that point, you’ll probably want to switch from listing the files to something like a bucket notification. And have your sensor pop messages from a queue: https://docs.aws.amazon.com/AmazonS3/latest/userguide/NotificationHowTo.html Unless your keys have a matching alphabetical and timestamp sort, it’s not possible with the S3 api alone to limit to only recently created keys when listing.