Thomas Trompette ec4e4740d2 Make workflow statuses more resilient (#12263) ...

Workflow statuses are often broken. I did not figured out why yet. But I
see two causes that can be fixed:
- statuses calculation are really complicated today, just to spare a
call to the database
- job is not indempotent, it is using the combination of the previous
statuses + the update to calculate the new statuses. Which means that
once broken, next updates will be broken as well

Instead, we now:
- fetch workflow versions
- get the statuses from these.
It simplifies the code and make the job indempotent.

2025-05-26 13:05:18 +00:00

..

twenty-chrome-extension

…

twenty-docker

…

twenty-e2e-testing

…

twenty-emails

…

twenty-front

Refactor drag selection: Replace external library with custom implementation and add auto-scroll (#12134)

2025-05-26 11:58:22 +02:00

twenty-server

Make workflow statuses more resilient (#12263)

2025-05-26 13:05:18 +00:00

twenty-shared

…

twenty-ui

…

twenty-utils

…

twenty-website

…

twenty-zapier

…