Details
-
Bug
-
Resolution: Fixed
-
None
-
Critical
-
When there is a longer time gap between steps in the import it may happen that the import crashes due race-conditions in saving the task meta table.
Description
problem
With the pricing preset the task meta data is saved on displaying the tasks in the UI.
On some imports (with a time gap between task creation and task upload handling) it happens that:
- task creation
- some one loads the tasks in the UI (inkl. the new task) → here the pricing preset feature makes a task meta save
- now the task upload and import is processed, now task meta is initialized new instead loaded from the disk: this leads to a duplicate key crash on saving it