Auto MPS Execution
This page explains how MPS execution works in Asprova Auto MPS.
There are two main ways to run an MPS:
- Scheduled execution — specify timings such as every day at 8:00, or every Tuesday and Friday at 13:00, and the MPS runs automatically at those times.
- Manual execution — run it whenever you like by pressing a button in the UI. Internally, this creates a one-time schedule.
If the server is offline when an execution is due, that execution is not run retroactively once the scheduled time is more than 30 minutes in the past. The next scheduled execution runs normally.
The lifecycle of execution
Every execution moves through a series of states, which you can follow from the project's Auto MPS screen:
| State | Meaning |
|---|---|
| Scheduled | The execution has been created and is waiting for its scheduled time. |
| Executing | The scheduling engine is currently processing the execution. |
| Succeeded | The execution finished successfully. |
| Finished with errors | The execution finished, but the scheduling engine reported one or more issues worth reviewing. |
| Failed | The execution could not be completed. |
| Timeout | The execution ran longer than the configured time limit and was stopped. |
| Aborted | The execution was stopped manually before it finished. |
| Cancelled | The execution was skipped before it started — for example, because the server was offline at its scheduled time and the time has since passed. |
Status: Finished with errors
The execution of the "main" scheduling parameter finished, but the status becomes Finished with errors when one or more of the following messages were output during the run. The full list of messages the scheduling engine can output is available in the Asprova Online Help.
- Messages in category "System" with level "Error"
- Messages in category "IO" with level "Error"
Following a run in real time
While an execution is running, its log is displayed live in the UI so you can watch progress as it happens. Once the run finishes, the results are saved with the execution so you can review them at any time.
Results and outputs
A successful execution stores the schedule it produced together with any supporting data generated during the run, such as production/sales/inventory (PSI) figures. These outputs remain available for review and download from the execution's page.
Data retention
To keep storage under control, each project can define a data retention period. Executions and their stored results older than this period are automatically removed. If no retention period is set, results are kept until you remove them.
Licensing
The current number of item codes counted against the limit can be viewed on the dashboard at any time.
Whether an MPS can be run is governed by your license and its usage.
-
Validity period — Auto MPS is available while your license is within its valid period. As the end of the period approaches, a message prompting license renewal is shown in the UI.
-
Usage limit — each validity period includes a limit on the number of item codes that can be processed. The server keeps a running count of item codes and notifies you in three stages:
- Approaching the limit — a warning is shown once the count comes within 50 item codes of the limit.
- At the limit — a warning is shown when the count is exactly equal to the limit. MPS runs are still allowed.
- Over the limit — once the count exceeds the limit, MPS runs are paused until the count resets in the next period or the limit is raised.
On demo licenses, item-code usage is still counted, but the limit is not enforced — MPS runs are never paused and the usage warnings are not shown.