If tomcat is down

Get Help & Discuss Process Studio
1

For instance, on an on-premise instance if tomcat is not running and an task is scheduled at the same time so, how will we know if the task is completed after server is back online?

2

If the Tomcat web server (which hosts the AE Server/UI) goes down on an on-premise instance while a scheduled task is set to fire, here is what happens and how you know whether it completed once the server comes back online:

1. How AE Server & ActiveMQ Handle the Event

  • Scheduled Trigger Missed: The trigger mechanism (managed by the AE Server scheduler) cannot fire while Tomcat is down. It will not execute retroactively on startup unless specifically configured as a retryable request.

  • Agent Status During Downtime: If the AE Agent was already executing a task before Tomcat went down, the agent continues running locally to completion. It holds its execution status in memory/local queues and attempts to re-establish connection to ActiveMQ/AE Server until the server responds.

2. How to Check Task Completion After Server is Back

Once Tomcat and the AE UI are back online:

Option A: Check AE UI (Requests & Tasks)

  1. Go to AE UI → Requests or Tasks → Execution History.

  2. Search for the specific Task Name or Request ID around the scheduled timestamp.

  3. Check the Status column:

    • Completed: The agent ran it and pushed logs back once Tomcat reconnected.

    • Failed / Error: The execution failed or lost state.

    • No Record / Not Triggered: Tomcat was completely down at the exact trigger time, meaning the scheduler never initiated the request.

Option B: Check Agent Logs Directly (The Ground Truth)

If you need definitive confirmation regardless of UI state, check the agent machine logs:

  • Open the log file on the Agent host at <AGENT_HOME>/logs/ or right-click the Agent tray icon → View Log.

  • Look for the workflow name (.psw) and its execution timestamp around the scheduled window.

When an on-premise AutomationEdge (Tomcat) server is down during a scheduled task’s trigger time, the platform manages and reports the status in the following way once the server comes back online:

1. What Happens During Server Downtime

  • Trigger Delay / Reschedule: If the server is offline at the exact time a schedule is set to trigger, the execution cannot initiate at that moment. By default, depending on schedule configurations, the scheduler will either run the missed task upon server recovery (if “Execute last skipped schedule” is enabled) or run at the next scheduled cycle.

  • 2. How to Check if the Task Completed After Server is Online

    Once Tomcat and the AE UI are back online, you can verify whether the task completed, failed, or was skipped using the following methods:

    A. Check the Requests Page (Requests Menu)

    Navigate to Requests in the AE UI to view the request history and check the Status column for your workflow:

    • Complete: The task was picked up by an Agent and executed successfully after the server came back online.
    • Failure: The task failed. Clicking on the row or failure description will display the exact reason (e.g., “Failed because the server was down” or connection failure).
    • Expired: The task request remained in the New state during server downtime and exceeded the server’s request validity clean-up threshold.
    • New / Execution Started: The task was picked up after startup and is currently queued or in progress.