You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a bug in the batch creation process where jobs that are not original to the new batch recipes (i.e. jobs that were created before and are being left as is in the new batch recipes) are still being added to the batch_job models for the batch. This creates the situation where a job belongs in multiple batch_job models, which is invalid and creates problems.
I believe the solution is to place a check in BatchManager._create_batch_models() so that only recipe_job models for new/original jobs (recipe_job.is_original is true) will create a corresponding batch_job model instead of all recipe_job models (which may contain jobs from previous batches).
Investigate and fix.
The text was updated successfully, but these errors were encountered:
There is a bug in the batch creation process where jobs that are not original to the new batch recipes (i.e. jobs that were created before and are being left as is in the new batch recipes) are still being added to the batch_job models for the batch. This creates the situation where a job belongs in multiple batch_job models, which is invalid and creates problems.
I believe the solution is to place a check in
BatchManager._create_batch_models()
so that only recipe_job models for new/original jobs (recipe_job.is_original
istrue
) will create a corresponding batch_job model instead of all recipe_job models (which may contain jobs from previous batches).Investigate and fix.
The text was updated successfully, but these errors were encountered: