Why does runZero only process data from one task at a time?

For any given Organization, the runZero platform will only process a single task's data at a time. This limitation is because of the need to ensure data is consistent and no information is lost.

Tasks have two phases:

1. Fetching data (either by scanning using an Explorer, or by connecting using an API connector).
2. Processing the data and updating assets.

The processing operation runs as follows:

1. The assets in the organization are loaded.
2. The scan data or imported data is processed, and the new information is merged into the assets.
3. The assets are written back to the database.

If multiple tasks' updates were processed at the same time for the same set of assets, the following could happen:

• Task A loads the assets from the database.
• Task A starts merging in new data.
• Task B loads the assets from the database.
• Task B starts merging in new data.
• Task A finishes work and writes the assets back.
• Task B finishes work and writes its copy of the assets back, overwriting all the updates from Task A.

Note that while only one task's data can be processed at a time for a given organization, the work of fetching data can run in parallel. That means multiple scans can occur at the same time, and API connectors can run in parallel with scans. However, the data collected will be processed one batch at a time.