Last Updated time for Deployment updates to current time when page is refreshed

[scottwalshqs]

First check

• I added a descriptive title to this issue.
• I used the GitHub search to find a similar issue and didn't find it.
• I searched the Prefect documentation for this issue.
• I checked that this issue is related to Prefect and not one of its dependencies.

Bug summary

After updating our Prefect Server to 2.19.8 (from 2.18.3), the Last Updated time for the Deployments changes to the current time when the deployment page is refreshed (instead of showing that actual time that the Deployment was last updated).

Reproduction

I was not able to reproduce this with a freshly installed Prefect Server.  :(

Error

No response

Versions (prefect version output)

Version:             2.19.8
API version:         0.8.4
Python version:      3.12.4
Git commit:          478e89d6
Built:               Thu, Jul 11, 2024 2:25 PM
OS/Arch:             linux/x86_64
Profile:             default
Server type:         server

Additional context

This is the behavior that I am observing:

Then I refresh:

[zhen0]

Thanks for raising @scottwalshqs - I am also unable to reproduce. I wonder if there's an edge case around your deployment or something that made this happen. If you're able to provide any further info, I'm happy to try reproduce again.

[scottwalshqs]

Thank you @zhen0. I rolled back our Prefect Server to 2.19.5, and the issue is now resolved. I chose 2.19.5 because I saw in the release notes for 2.19.6 some bug fixes for deployment statuses, which seemed like they could be related to my issue. Maybe the changes in 2.19.6 are related to the issue I am seeing in 2.19.8. If it's helpful, I can update to 2.19.6 directly to further isolate the issue.

[zhen0]

Thanks. It still strikes me as very odd. Do let us know if you are able to narrow it down further.

[scottwalshqs]

@zhen0 The bug does NOT exist in 2.19.5, but it does exist in 2.19.6. So I have isolated this bug to 2.19.6. Hopefully this is a narrow enough scope to work with.

[scottwalshqs]

Maybe it has to with this this background task that was added: 62f0db6.

We do rely heavily on work queues right now.