Closed guillaumeNaimi closed 4 years ago
It's the normal behavior for now ...
What do you want ? If the changeset is marked as ERROR, stop the process ?
This is a normal behavior from my point of view :
That's mean, if a changeset has failed, we need to see in DB the cause, fix it and mark this entry as RESOLVED and restart the update
When the update is KO, updatarium say when you relaunch it that it has already been executed in error and don't relaunch the changeset