Hi, we are getting some spurious alerts from prefe...
# prefect-cloud
n
Hi, we are getting some spurious alerts from prefect-cloud: This alert is configured to trigger if a flow-run remains in
Late
or
Pending
state for over 10 minutes, but we are seeing this even if the flow completed successfully and in less than 10 minutes.
Prefect flow Late or Pending for over 10 minutes
Flow run build-meta/spectral-anteater entered state
Completed
at 2023-02-15T193953.508606+00:00.
Flow run URL: https://app.prefect.cloud/account/adee12e2-25d9-428a-9a77-32d8d7ca2ac7/workspace/28562586-0812-4e92-803f-99ce64384cbd/flow-runs/flow-run/81433951-84a0-4bb1-95e9-22a942912d3a
State message: All states completed.
w
Hi @Nikhil Jain - thanks for flagging this. We’re currently making some improvements to flow run state triggers, these changes will ensure better reliability on this front. Would you mind filing an issue in our github repo with relevant account, workspace, and automation information so i can ensure our changes address your concerns? Thanks.
n
thanks @Will Raphaelson I see a similar bug report: https://github.com/PrefectHQ/prefect/issues/8217 I added a comment there. Do you think it’s the same issue or should I file a new bug?
w
Thanks Nikhil, I think we can just work off that issue.
c
Thanks @Nikhil Jain we've released a change today that will majorly help with this situation: https://github.com/PrefectHQ/prefect/issues/8217#issuecomment-1435053046
🙏 1
n
@Chris Guidry @Will Raphaelson This issue is still happening for us (example below). Should I file a new bug?
Prefect flow Late or Pending for over 30 minutes
Flow run build-meta/gainful-parrot entered state
Completed
at 2023-02-22T191501.319309+00:00.
Flow run URL: https://app.prefect.cloud/account/adee12e2-25d9-428a-9a77-32d8d7ca2ac7/workspace/28562586-0812-4e92-803f-99ce64384cbd/flow-runs/flow-run/f19f54e2-0399-4930-a433-7f13f02d57d4
State message: All states completed.
i
This is also happening for us just FYI
🙋 1
c
Thanks Nikhil and Ilya, we're still working on other variations of this issue and are expecting to have this resolved in production before the end of the week. Sorry for the delays!