Engine Activations
Activating individual configurations of some engines and triggering them according to a schedule that is specified in the activation and can be customized to your preferences
Table of Contents
Activating individual configurations of some engines and triggering them according to a schedule that is specified in the activation and can be customized to your preferences.
Overview
Engine activations allow activating individual configurations of some engines and are triggered according to a schedule that is specified in the activation and can be customized to your preferences.
How to create Engine Activations
For example, to create an engine activation for a specific configuration of the Start Custom Workflow, perform the following steps:
- Start Matrix42 Enterprise Service Management and open the Administration application.
- In the navigation area, click Services & Processes → Engine Activations.
- On the toolbar, click + Add Engine Activation action to open the New Engine Activation dialog.
- In General view, fill in the Name field, for example, Start Custom Workflow:
- In the Activated Engines, click + icon to add activated engines:
- Engine to be Activated: click the single selection (loupe) button in the Engine to be Activated field to open the list of available engines.As an example, find the Start Workflow engine and click Select.
- Starts After: It is required to save Engine Activation before you can specify it in "Starts After" field for another Engine(s). Select from the list of available Activated Engines,
- Notes: optional notes for the configuration
- Engine Activation Parameters depend on the selected Engine to be Activated. In the example case, select the workflow to be activated.
- Click Finish to save the changes for the engine.
-
Schedules lists the configured schedule for the Engine Activation. Click + icon to create a new schedule:
- In the Add new schedule dialog, fill in the following data:
- Schedule Name
- Start From: the date since when the schedule starts running and the time of the day when the activation will be run. Define the date, time, and time zone.
-
Repeat: Set the frequency for executing the activation. Available options:
-
By Time: in minutes specify how often the engine activation should be re-run, e.g., to repeat every hour, set 60; every 2 hours - set 120 minutes, etc.
The minimal possible frequency is 1 minute.
- Daily: for this option, specify how often the engine should be re-run, e.g, when the Repeat every (days) is set to 1, the Engine activation will be run once every day at the specified Runtime.
-
Weekly: set when to repeat the engine running and specify on which days of the week
-
Monthly:
-
Day of the month: specify the day of the month and how often it should be repeated, e,g, to run the engine activation every month on the 1st day of the month, set Day to 1 and Repeat every (months) to 1

-
Day of the week: in the Pick a value field, specify the week number of the month (First, Second, Third, Fourth, Last), the Day of a Week, and Repeat every (months)
-
Day of the month: specify the day of the month and how often it should be repeated, e,g, to run the engine activation every month on the 1st day of the month, set Day to 1 and Repeat every (months) to 1
-
Yearly:
-
Date: choose the month and the day of the month when the engine should be run
-
Date: choose the month and the day of the month when the engine should be run
-
Day of the month: specify the Week of Month (First, Second, Third, Fourth, Last), the Day of a Week, and choose the Month
-
By Time: in minutes specify how often the engine activation should be re-run, e.g., to repeat every hour, set 60; every 2 hours - set 120 minutes, etc.
-
End: Select the time range within which this schedule should be in effect. Choose one of the options:
- Never
-
After a number of recurrences: set how many times the engine activation should be re-run
-
On Date: set a specific date that defines the end date
- Click Finish to save the changes.
- Click Save & Close to save the changes for the engine.
How to Enable/Disable Engine Activations
By default, every new Engine Activation is created with status "Enable". If you want to disable Engine Activation you can use Action "Disable" or edit Engine Activation and select the "Disable Entire Activation" checkbox in the dialog.
How to Activate Engine Activations
You can use Action "Activate":
- Select your Engine Activation
- In the action panel click action "Activate"
- In popup message click ‘Yes’
Standard Engine Activations
| # | Name | Description |
|---|---|---|
| 1 | Account Unlock |
Unlocking of user accounts that have been locked due to exceeding the maximum number of failed login attempts. By default, runs every minute. See also, Sign-Up & Password Recovery. |
| 2 | AD Connector | |
| 3 | Archiving Activation |
Archives weekly old Incidents into the archive database. Runs every Saturday at 8:00 PM UTC. See also, Archiving outdated incidents. |
| 4 | Asset Management - Data Batch Processing |
Daily runs the asset manager data processing engine. Runs daily at 12:00 AM UTC. |
| 5 | Clean Up Obsolete Objects |
Cleaning obsolete Workflow Instances. Runs once a day at 1:00 AM UTC. See also, Workflow Engine: Cleaning Obsolete Workflow Instances. |
| 6 | Contract Management - Data Batch Processing | |
| 7 | Data Provider Activation | |
| 8 | Database Maintenance | |
| 9 | Datacenter Compliance | Runs daily and imports and updates Datacenter inventory data. |
| 10 | Escalation Management |
Runs every 5 minutes and checks tickets with reached solution reaction point. The tickets are escalated: the responsilbes are notified via email and a record is added to the ticket journal. See also, Service Desk E-mail Notifications. |
| 11 | ESM Certificates Deployment |
Triggers the synchronization process for ESM Certificates. This is particularly useful when there is a need to apply recently purchased product certificates to the environment promptly, rather than waiting for the scheduled automatic synchronization, which occurs weekly. See also, License Certificates. |
| 12 | File Storage Uploads Reviewer | |
| 13 | History Consolidation |
Daily consolidation of collected data changes in the archive database. Automatically collects and consolidates history data related to changes in Configuration Item objects within the Matrix42 system. Runs daily at 12:00 AM UTC. Is also activated when a user manually triggers the consolidation process by using the Force Consolidation option in the History Wizard. See also, History Wizard. |
| 14 | Inventory Activation | |
| 15 | License Management - Data Batch Processing |
Daily runs the license manager data processing engine. Runs every day at 11:00 PM UTC. |
| 16 | License Management - Recalculate Statistics |
This activation runs software, license inventory and license requirements statistics recalculation. Runs every 2 hours. |
| 17 | License Management - Remote Usage Configuration | |
| 18 | License Management - Start License Requirements Reconciliation |
This activation handles commands to start License Requirements Reconciliation workflow. Runs every minute. |
| 19 | License Management - Update Reporting Data Warehouse |
Continuous Data Warehouse Update And Cube Processing. Runs every hour. |
| 20 | License Management - Usage Data Processing | |
| 21 | Login Tracking Cleaner | |
| 22 | M42Next Data Ingesting |
Upload of data to M42Next (cloud platform to enable AI and data driven capabilities). See also, AI Search Configuration: Ingesting Data |
| 23 | Microsoft Entra ID Data Provider |
Scheduled run for Microsoft Entra ID Data Provider. Runs every hour. |
| 24 | Process Compliance Rules - Date Conditions |
Executes compliance rules that contain date conditions. Runs every day at 11:05 PM UTC. |
| 25 | Process Compliance Rules - Delayed |
This activation runs compliance rules processing in long cycles and will handle events for all compliance rules that are set for delayed processing. Runs every day at 11:00 PM UTC. See also, Compliance Rules. |
| 26 | Process Compliance Rules - Immediately |
This activation runs compliance rules processing in short cycles and will handle events for all compliance rules that are set for immediate processing. Runs every minute. See also, Compliance Rules. |
| 27 | Process Report Subscriptions |
Run daily to ensure that users receive their subscribed reports and dashboards via email according to the specified schedule. Runs once a day at 3:00 AM UTC+02:00 See also, Subscribe to Dashboards and Reports and Report Subscriptions. |
| 28 | Process User Type Determining | |
| 29 | Roll Log Files |
Daily checks for old logs and removes them if necessary. Runce once a day at 6:10 PM UTC. See also, System Diagnostics and Server Logs. |
| 30 | SCCM / Enterprise Manager - Data Import |
Daily imports inventory data using Enterprise Manager API or directly from System Center Configuration Manager. Runs once a day at 11:00 PM UTC |
| 31 | SCCM / Enterprise Manager - Service Installation Checker |
Checks service installation/uninstallation status using Enterprise Manager API or directly on System Center Configuration Manager. Runs every 5 minutes. |
| 32 | Service Booking Reconciliation |
Detects the actual usage of services and generates the respective services bookings if they don't exist. Runs once a week at 10:00 PM on Sundays. See also, Service Demand Detection and Simple Services Configuration. |
| 33 | Service Catalog - Shopping Card reminder |
Runs weekly to send email reminders to the users who have added services to their shopping cart but have not completed their orders. Runs once a week at 03:00 PM on Mondays. See also, Service Catalog Settings: Inform requesters about unordered Services in their Shopping Cart property |
| 34 | Service Connection Validation | |
| 35 | Service Desk - Responsible Reminder |
Sends mail to the Ticket Responsible in order to remind about no progress on ticket(s). Runs every day at 8:00 AM UTC+01:00. |
| 36 | Service Desk Service Availability Change Communicator |
Checks Change Requests and updates the affected service health status and adds comunication update to the SAC dashboard. Runs every 15 minutes. See also, Service Availability Center (SAC). |
| 37 | Service Management - Automatic Closing of Incident |
Checks Incidents and Service Requests on Resolved state and closes them if the Close resolved ticket when no user feedback is provided property was enabled and configured. Runs once a day at 1:00 PM UTC. See also, Service Desk global settings and E-Mail Robot: Close resolved ticket when no user feedback is provided property. |
| 38 | Service Management - Inbound Mail Robot |
E-Mail Robot monitors mailboxes and, from the ticket IDs in the subject line, checks whether these tickets already exist in Matrix42 Service Desk and adds the information to it or creates a new one. Runs every 15 minutes. |
| 39 | Setup calculated attributes Engine Activation | |
| 40 | Storage Files Clean Up | |
| 41 | Storage Recycling | |
| 42 | Workflow Engine Health Check |
Runs every hour. See also, Workflows Health Check. |
| 43 | Workflow Instances Rehydration for Worker |
Refers to the process of restoring a workflow instance from a persisted state in the database. This is particularly important for long-running workflows that may need to be resumed after being suspended or interrupted due to various reasons, such as application restarts or system failures. If the workflow instance fails or is unable to continue, it can be rehydrated from this stored state, allowing it to resume execution from the last persisted point. This process ensures that workflows can continue seamlessly, even after interruptions, thereby enhancing reliability and reducing the risk of data loss. Runs every hour. |
| 44 | Workflow Monitoring Auto-Purge |
The auto-purge function is configured to run automatically once a day at night. When the Monitoring Database exceeds the specified size, the system will automatically remove the oldest monitoring records to free up space. Runs once a day at 12:30 AM UTC. |