Tasks occasionally get stuck

Support
1

Hello,

We are experiencing an issue on our EasyMorph Server where tasks occasionally get stuck. The task status shows as running, but it never completes. When we try to cancel the task, it doesn’t work either.

The only way to resolve this is to stop the EasyMorph Server service and restart it.

We are currently on version 5.9.7.34, but this problem has occurred in earlier versions as well. It also happens with different tasks each time, not the same one repeatedly.

Could you advise on what might be causing this and how we can prevent it?

2

Check if you have too many browser tabs open with EasyMorph Server pages. Browsers have limits for simultaneous connections to the same site, so it many tabs are open for the same site it may lead to real-time updates stopping - a task is running, but the UI "freezes" and doesn't reflect any changes in the task state.

3

It’s not just the UI that is stuck,the task is really blocked. After a restart of the service the task will get triggered again but there will be an gap in the history. Also we see that no tables have been updated, no files created, etc. so it’s really the task not running anymore.

4

I see. Can you tell a bit more about the machine where the task is executed - is it a virtual machine or not? How many CPU cores/threads and RAM does it have?

Also, do you run the task in the Default worker or in a separate Server worker?

5

It’s a virtual machine with 12 cores and 24 GB RAM. RAM usage is high from time to time.

We only have one worker.

6

Hi,

You mentioned that certain tasks occasionally become stuck, requiring a server restart.

We are experiencing an issue on our EasyMorph Server where tasks occasionally get stuck

Could you confirm whether this behavior is specific to certain tasks?
Are these tasks running on the Default worker or another worker?

When a task becomes stuck, is the server still responsive, for example, can you launch other tasks or download files?

If specific tasks regularly encounter this issue, please enable the Diagnostic Log option in each affected task's settings, ensuring a separate log file is generated per task. Should the issue occur again, please forward this log file to support.

Additionally to these logs, please provide the Server Debug log files covering the period from before the task started until the moment the server was restarted.

7

It’s not the same task, but different tasks everytime.

When a task is blocked, the server and any other tasks still run fine.

The tasks are running on the default worker.

I’ll send the log files to the support mailbox.