You may sometimes wonder why BeLazy creates a new project or task when all the bundling conditions appear to be met. Bundling does not depend only on the metadata of the incoming projects, it also depends on the current status of the project in the business management system (BMS). In BeLazy jargon, we call this status "frozen." A frozen task is one that BeLazy will no longer merge new work into, so any incoming project that matches your merging rule will land in a new task instead of joining the existing one.


The reason for this design: once a vendor has been assigned or a job is in progress, retroactively adding new scope to that task could corrupt data in the BMS or silently expand work that is already committed to a vendor. Freezing the task protects both your BMS state and your vendor relationships.


If you are using BeLazy's BMS REST API or XTRF Smart Projects, the destination is never frozen. Bundling will always merge into the existing task or job when the merging rule matches, regardless of progress.


In Plunet, an item is frozen as soon as either:

  • the item status is anything other than NewAuto or InPreparation. Any other status (InProgress, Delivered, Approved, etc.) forces BeLazy to create a new item even when the merging rule matches.
  • any of its jobs is in a status other than InPreparation, Requested, or AssignedWaiting. As soon as a single job on the item moves to InProgress or beyond, the whole item is frozen, not just that job.


In Protemos, tasks are frozen as soon as any job in the tracked job chain (the workflow chain associated with the merging rule) has started. Jobs are considered "not started" while in Draft, OfferedToVendor, Active, or OfferRejected. Any other status (Started, Completed, CompletionAccepted, Canceled, and so on) freezes the task.


In XTRF Classic, tasks are frozen unless the task status is OPENED and every job on the task is in OPENED or ACCEPTED. Any other task status, or any job in a different status, freezes the task.


Once an item or task is frozen, it cannot be "un-frozen" for merging purposes. New incoming work will always land in a fresh item or task, even if you revert the BMS status afterwards. For work to bundle, the new project must arrive before the destination enters a frozen state.