Open fatchat opened 1 month ago
Someone else was running it, so the system user
couldn't lock it in the webhook
I am guessing something similar for the other deployment.
In both cases, can't say who triggered the pipeline (can say who did not triggered the pipeline). Would be nice to the orguser_id
ok so it's not an error because the tasks are already locked
inwebhook_api.lock_tasks_for_pending_deployment
we are catching the exceptions thrown by prefect_service.lock_tasks_for_deployment
... so why is grafana seeing them
Hmmm, no idea. I need to check the alerting logic.
Yes... not urgent it's just annoying because we get the emails