Issue:

While executing a scheduler-triggered workflow request, the following error is displayed:

"Invalid host: License not created for the current host"

The environment had two Tomcat instances running without HA configuration, and both instances were connected to the same AutomationEdge database.

Cause:

Quartz uses the database as its job store, so both Tomcat instances could pick up scheduled jobs.

The second Tomcat instance was running on a machine whose MAC address was not included in the AutomationEdge license. Therefore, requests processed by the second instance failed with the "Invalid host: License not created for the current host" error.

The issue was confirmed by checking the source_ip column in the ae_schedule_firetime_history table, where scheduled executions were found from two different IP addresses.

Resolution:

1. Check whether multiple Tomcat instances are running and connected to the same database.
2. For a single-server setup, stop the unintended Tomcat instance and ensure only the licensed server processes scheduled jobs.
3. Verify that the MAC address of the active server is included in the AutomationEdge license.
4. If multiple Tomcat instances are required, configure the environment in HA mode and ensure the required licensing is in place.
5. Use the following query to identify the source IP of scheduled executions:

SELECT source_ip, created_date 
FROM public.ae_schedule_firetime_history
WHERE DATE(created_date) = '2026-08-20' 
ORDER BY created_date DESC;

6. If multiple source_ip values are returned, identify the corresponding servers and verify which Tomcat instance is processing the schedules.
7. You can stop the Tomcat service on the second instance if a high availability setup is not configured. Or, if you need to use a HA setup, update the license file with the MAC address of the second server, and upload the updated license to the AutomationEdge server where the second instance is running.

Additional Notes:

• In a single-server setup, scheduled executions should originate only from the expected server.
• Multiple Tomcat instances connected to the same database can pick up scheduled jobs because Quartz uses the database as its job store.
• The source_ip column in ae_schedule_firetime_history can help identify the server that executed a scheduled job.
• If multiple source IP addresses are found, verify whether an additional Tomcat instance is running or processing scheduled jobs.
• The AutomationEdge license must match the MAC address of the server on which the licensed instance is running.