Problem

If a segment with a lot of repetitions is saved or if the AutoQA takes long, the user is able to leave and finish the task even if the repetitions saving is still in progress. Finishing the task will trigger multiple workflow related actions and one of those actions is the trigger callback action. For external systems, which are relaying on this action, the closed task means that the task is finished and they for example will trigger export in translate5. This kind of export can be incomplete(no all segments are saved) because of the pending alikes/repetition saver.

To reproduce

• Create simple file with segment with a lot of repetitions
• import the file and assign user to the task
• edit and save the segment with a lot of repetitions
• while the alike save is pending leave and finish the task

Additional todo: similar problem on ordinary task save

• save segment, add a 10 second delay to the termtagger service (which was surly the reason in TS-3746)
• Then leave the task
• At the point of time of task leaving the segment was not yet in the DB
• In TS-3746 this was a crucial problem, since task finish was directly triggering the export and was not getting the last edited segment

Solution

One way to solve this problem is UI block to leave the task while there are pending changes, in other words: block task actions when there are some running XHR requests.

Additional notes after talk with the team

We just did confirm the idea above with the prompting users when requests are running. We can hook on the on window close event and show the info message to the user. Same as https://app.ctl.inetsolutions.cloud/ is doing when you try to close the window.