Schedule unplannable workload via static runtime

A system for scheduling unplannable workloads via static runtime, comprising:

• at least one processor;
• and
• a memory storing instructions therein that, when executed by the at least one processor, cause the at least one processor to perform operations comprising:
• establishing an inbound channel based on a setup order and associating the inbound channel to an Ingestion-Transformation-Load (ITL) task;
• storing incoming data received via the inbound channel to a staging area;
• organizing the incoming data in the staging area into a plurality of batches;
• monitoring the staging area to determine a number of unprocessed batches;
• and
• generating a work order for each of the plurality of batches in the staging area in response to determining that the number of unprocessed batches meets or exceeds a first predetermined threshold;
• assigning a priority number to the work order generated for each of the plurality of batches;
• executing work orders on a runtime instance in a sequence based on the priority number assigned to each of the work orders;
• and
• removing data in a batch corresponding to the work order being executed on the runtime instance from the staging area when a status for the batch indicates that the batch has been processed and loaded to a target.

A non-transitory computer-readable medium having instructions stored thereon that, when executed by at least one computing device, cause the at least one computing device to perform operations comprising:

• establishing an inbound channel based on a setup order and associating the inbound channel to an Ingestion-Transformation-Load (ITL) task;
• storing incoming data received via the inbound channel to a staging area;
• organizing the incoming data in the staging area into a plurality of batches;
• monitoring the staging area to determine a number of unprocessed batches;
• and
• generating a work order for each of the plurality of batches in the staging area in response to determining that the number of unprocessed batches meets or exceeds a first predetermined threshold;
• assigning a priority number to the work order generated for each of the plurality of batches;
• executing work orders on a runtime instance in a sequence based on the priority number assigned to each of the work orders;
• and
• removing data in a batch corresponding to the work order being executed on the runtime instance from the staging area when a status for the batch indicates that the batch has been processed and loaded to a target.