Easymorph server task running one hour late

Server
1

Hello,

Recently we had an issue with a task on Easymorph server, which was supposed to run at 7AM, but only started at 8AM without any apparent reason.

We are using the default service account in the server, I guess there are no limitations on the runs, and we didn't face any memory issues during that hour.

Do you know if due to the number of tasks running at 7AM, it was postponed to run one hour later? Is there any configuration on server side that might justify this issue?

Any ideas are welcome, since I cannot find a reason on my side.

Thanks in advance.

Best regards

2

Hello Gorito,

A few questions:

  • What's the version of your EasyMorph Server?
  • What timezone is set for the Windows machine that runs EasyMorph Server?
  • What timezone is set on your machine?
  • When you open the Tasks tab on EasyMorph Server, do you see a yellow warning that the time in your browser is different from the Server time?
3

Hello Dgudkov,

The server version is 5.7.3.1.
The schedule times in the Server are 1h ahead of my local time, but has always been like that and it's the first time I've noticed this issue.

Just to give you an example, I have a task that runs everyday at 7AM. Last week the task in the server " Finished workflows" log tab has a time of 9h02mins which means it finished around 9AM, and a "Elapsed" time of 2h2m39s.
We have a status message to show in the logs whenever the task starts running, and this message came at 8:01 AM.
My idea, and according to the time shown for the task to finish, it was triggered by the server at the usual time, but only started the process one hour later.

That's why I'm wondering if we have any mechanism in the server which prevents a task to run whenever the server is low on memory (which I think it was not the case from our logs) or some other thing.

4

Hi! Is it possible that the workflow began immediately after the schedule was triggered, but some initial steps in the workflow itself caused it to take ~ an hour longer?

5

Hello,

We have a Status message when we start the workflow, and that message came 1 hour after.

6

Hi

Please provide the following information for further investigation by sending it to our support email:

  • Debug logs: Please send the debug logs for this period, typically found at C:\ProgramData\EasyMorph Server\Logs\Debug log.
  • Project Name: Specify the project name involved.
  • Task GUID: This can be found in the URL when you open the task in your browser. For example, in the URL http://corp:6330/space/w/tasks/edit/40ba585b-5512-4a05-bdb5-537383d0e7a2/properties, the task GUID is "40ba585b-5512-4a05-bdb5-537383d0e7a2".
  • Schedule Screenshot: Attach a screenshot of the task schedule.

Additionally, please verify if there were any changes made to this task during or just before the specified period by checking in the Journal - User Actions section of the server's admin area. Use the event filter Applied filter:Action is edited task to identify any modifications that might have altered the task's start time.