My job failed but didn t retry

Question

My job failed but didn t retry Other jobs seem to be working fine

Liezl Puzon · Answer

the same instance of the live pricing op highmem job from earlier DID retry <https nautilus dagster cloud prod instance runs 802ff731 5b47 4bba 87ae 632eba0bcd3c logKey=live pricing op highmem>

johann · Answer

Hmm is it possible your agent went down around that time

Liezl Puzon · Answer

could be possible is there a way to gracefully recover in that case

Liezl Puzon · Answer

guess it might require more of an external monitoring solution use graphql to force a job to restart if the run post conditions aren t fulfilled

johann · Answer

Since it seems like this was an ephemeral issue I think we should expand the retry policy to retry this type of failure not being able to connect with your user code when launching the retry run