https://prefect.io logo
m

Moe

08/02/2023, 3:17 PM
Hi, My prefect flow was running fine for 2 days scheduled every 2 hours. But now they are failing with no helpful information in logs. My work queue is healthy and my flow is deployed on ECS where the worker is always running. I am using git clone step in my deployment, the logs just say
Cloning into Repo....
and it goes into pending for 8 hours or so before failing or just gets stuck in pending. Anyone experienced this before? How to resolve this?
d

Dominic Tarro

08/02/2023, 4:00 PM
Did your repository key expire, maybe a change in permissions that has it hung at a particular stage?
m

Moe

08/02/2023, 4:18 PM
No, my repo key doesn't expire for next 11 months. No changes in permissions.
a

Arnaud

08/14/2023, 6:31 AM
Hi @Moe Dou you have more information on this problem? I am facing the same problems with some of my flows.
m

Moe

08/14/2023, 3:07 PM
@Arnaud I switched to using git credentials with prefect git credentials block. Instead of the gitlab access token. Everything is fine now.
I suspect it's a problem related to actual gitlab access token or the access token prefect block. But didn't get to confirm. Let me know if you found anything.
s

Serina

08/23/2023, 9:57 PM
We believe it’s to do with the way we’re handling the access token during
git_clone
but we’re actively working on this fix/enhancement! If you end up confirming anything on your end, feel free to add updates to the thread and I’ll try to do the same for posterity.
🙌 1
thank you 1
An update: this fix has been released, so you should be able to use
GitLabCredentials
and
BitBucketCredentials
without issue! You can checkout the PR here: https://github.com/PrefectHQ/prefect/pull/10555