My job failed but didn’t retry <https://nautilus.d...
# ask-community
Hmm, is it possible your agent went down around that time?
could be possible. is there a way to gracefully recover in that case?
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?
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)
❤️ 1
🙏 1