Closed amaltaro closed 4 years ago
@amaltaro I was considering both options (marking them as done and also not marking them) but at the end I deliberately left the workflows worked in DRY-RUN mode as not marked, because we at the end, do not act on any of them. And also if we mark them then we would have only a single log of no more than 30 workflows in testbed and that wouould be our whole testing sample, which I considered quite not enough. But yes, you are right about the historical records in the database. I will switch the behavior of the service.
Thanks Todor. There is no need to push it over the weekend though - I do not think it's a blocker for production - so we can target the August production deployment.
Totally agreed!
Impact of the bug ReqMgr2MS - MSOutput
Describe the bug If workflows don't get marked as done, they will keep getting evaluated cycle after cycle. Which means, once the service is fully enabled in production, it will go through all the previous documents already available in the database (unless we drop the database during the deployment).
How to reproduce it none
Expected behavior Once MSOutputConsumer has successfully consumed a workflow output placement - be the service fully operational or in dry-run mode - we should update the transfer document and mark it as
done
, such that that workflow doesn't come up again in the next cycle. Of course, if there is any error while handling that workflow, then it still needs to be kept for the future cycles.In addition to this, we should distinguish between dry-run mode and broken transfer submission, such that we know what can be marked as done or not, instead of:
Additional context and error message One example among many others in the logs in vocms0731: