@Marvin, We recently upgraded to Prefect version 3.6.24, and since then we’ve started encountering an issue. Some of our tasks are completing successfully (as confirmed by the logs), but their state in the Postgres database remains stuck as “running.” Because of this, our flows are not progressing to subsequent tasks. We did not face this issue prior to the upgrade. In addition to upgrading Prefect, we also migrated to a multi-worker architecture, where we are now running four workers along with a Redis server. Prefect server and services running separately. Could you help us identify the root cause of this behavior and suggest how we can resolve it?

❌ Error: GitHub authentication failed

@Marvin, We recently upgraded to Prefect version 3.6.24, and since then we’ve started encountering an issue. Some of our tasks are completing successfully (as confirmed by the logs), but their state in the Postgres database remains stuck as “running.” Because of this, our flows are not progressing to subsequent tasks. We did not face this issue prior to the upgrade. In addition to upgrading Prefect, we also migrated to a multi-worker architecture, where we are now running four workers along with a Redis server. Prefect server and services running separately. Could you help us identify the root cause of this behavior and suggest how we can resolve it?

❌ Error: GitHub authentication failed