[🐛 Bug]: Workflows revisions show the same dates

[akire0ne]

Describe the bug
Workflows with multiple revisions entries under "Versions" shows the same timestamps across all revisions

To Reproduce
Steps to reproduce the behavior:

• Create any new valid workflow
• Save it
• Edit it multiples times
• Go to "Versions" on the Workflow Detail
• Multiple versions are shown, with all the same timestamp

Expected behavior
Timestamp should be accurate across revisions

Screenshots

Additional context
Keep 0.45.0

[dosubot]

There are known issues in Keep 0.45.0 where workflow revisions display the same timestamp across all versions. This is likely related to how timestamps are managed in the backend. The relevant fields (updated_at in WorkflowVersion and last_updated in Workflow) are configured to use the current timestamp by default, but the code that creates or updates workflow revisions often sets these fields directly using datetime.now(). This can lead to all revisions having the same timestamp if the value is not updated correctly or if the timezone handling is inconsistent. There is also no explicit enforcement of UTC or timezone awareness across the codebase, which can further contribute to this issue. Migration scripts and recent changes to workflow versioning may also play a role, especially if the database schema is not fully up to date or if migrations did not apply as expected [source] [source] [source].

To address this, ensure your database schema is up to date with the latest migrations, and review the code paths that set the updated_at and last_updated fields to confirm they are being set with the correct, current timestamp for each revision. If you are using SQLite, be aware of known migration issues that may affect timestamp handling.

To reply, just mention my name @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}