Is there a way to force the sensor process to reload code or understand how long it will take before a code update happens? (for context) I would like to not rely on reties which seems like the current path without knowing

Hi @nickvazz - do you know i you running your own gRPC servers here (or running in docker/k8s/something that manages user code servers for you)? Or relying on the daemon to spin the gRPC servers up locally for you?

I have done both using the daemon and running the gRPC api locally, although I have yet to try using the docker gRPC deployment option

Got it - the daemon reloads code from your gRPC server every 60 seconds, I believe

So forcing a retry delay on the the job it tries to create should generally work then it seems like