Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Prefect Community

Hi, my job code was suddenly stopped with `prefect.exceptions.TerminationSignal` exception. The flow run page shows this message under the title:
```Failed due to a(n) KeyError in the Prefect flow run worker. The error originated from not being able to determine the exit code for a job and reporting it as -1.```
Flow definition in my code has `retries=5` configuration, but no retries were issued.
Manual retry did solve the issue.
Sounds like Prefect internal error. Did anyone encounter it? Anyone has a solution?

Hey Kosta, thanks for raising. Hmm- was your worker healthy around the time that this happened? Is this the full stack trace of the error?

What sort of infrastructure are you using?

The only mention of KeyError is in a one-liner at the to of Prefect UI:

Screenshot 2023-11-09 at 13.38.16.png

(It is in completed state because of a manual retry later)

This is a screenshot of additional logs from Prefect UI

Screenshot 2023-11-09 at 13.40.20.png

<@U03FYEHGY57>, what do you want to know in terms of infrastructure? We are using Prefect workers.