A Job in Makersite can be an import, deletion, calculation, data enrichment, report creation, or any other background task Makersite performs relating to data.
The Jobs list can be used to check the status of a Job that has been started. For example, if you deleted a folder, you can go to the Jobs page and confirm that the deletion process has Finished.
To access the Jobs page, click on the User Menu in the top right corner of any Makersite page, and select Jobs from the list.
Status Definitions
Status | Description |
Queued | The job is put into the queue for calculation. |
Started | The job has been taken from the queue and is in progress. |
Finished | The job has been successfully finalized. |
Failed | The job has failed and should be redone. If it after a second trial still fails, contact [email protected]. |
Lost | Makersite was not able to retrieve the job reference. Therefore the status of the job is unknown. If the job was successful a notification email should be retrieved, else retry or contact [email protected]. |
Job Types and Queues
Makersite recognizes multiple types of jobs and assigns them to several different queues to optimize performance, as described in the table below.
Job Queue | Job Types | Explanation |
deleter | Folder Deletion | Triggered whenever you delete a folder in your MyDrive. |
sharing | Item Sharing | Any sharing operation in Makersite, such as sharing an imported BOM with a team member. |
reports | Background report calculation | Runs whenever you create a report with the Run in background and save option or when you don't select it but Makersite decides that the report is so big it needs to be queued. |
enrichment | Enriching geographies, Chemistry Enrichment, Product enrichment, MakerSite AI Gap-filling, SKU Enrichment, Substance Enrichment | All enrichment tasks in Makersite. |
priority | Qa Script (to be moved), Creating advanced alternative (to be moved), Disabling advanced alternative (to be moved), User initiated Impact Calculation, User initiated Environmental Impact Calculation, Generate LC Model, Delete LC Model | Priority queue takes all manually triggered calculations. All priority jobs have the _prio suffix appended to task in the UI. For example, selecting Recalculate LC models on a product should result in a job in the priority queue. |
importer | All IPC imports and other non-BOM imports (suppliers, transactions, etc.) | Self-explanatory. |
bomimporter | BOM Import | All BOM imports which require asynchronous queueing (larger than 250 rows). Smaller BOMs are not queued. |
postprocessor | BOM IPC Enrichment, BOM Post-processing, Import QA | Queue used for maintenance tasks. |
impacts | Environmental Impact Calculation | All impact calculation jobs which are not user-triggered (these go to priority) but automatic (for example caused by a change in product alternatives). |
Column Explanation
Column | Description |
Task | Job name. If the job has the _prio suffix, it is allocated to the priority queue. This is reserved for calculations triggered manually by the user. For example, changing an alternative in a product model should not trigger a priority. |
Job Type | Describes what this job is doing. See Job Types above for more details. |
Status | See Status Definitions above for more details. |
Start on/Finished on | Job start and finish dates. |
Owner | Account which started this job. Teammates can see each other's jobs. |
Error message | If the job failed, the error message is displayed here. |
Actions | Menu with available actions. You can use it to delete a job. |