Hi Giacomo,

I know there have been a few issues with stuck tasks with the older versions of NA.  

On core 1, do you see an event for memory?  If so, you can try to connect to the proxy and do a "run gc" and this might help.  

Other option, look at the queued tasks and try to cancel a few or cancel all and re-run the cancelled task and see if runs cleanly.  

Can you say if your NA configuration has devices bound to a core or not?  

thanks,

Chris

Hi Giacomo,

I know there have been a few issues with stuck tasks with the older versions of NA.  

On core 1, do you see an event for memory?  If so, you can try to connect to the proxy and do a "run gc" and this might help.  

Other option, look at the queued tasks and try to cancel a few or cancel all and re-run the cancelled task and see if runs cleanly.  

Can you say if your NA configuration has devices bound to a core or not?  

thanks,

Chris

Hello Chris,

doing top on the server this is the result

KiB Mem : 32761312 total, 226768 free, 31490604 used, 1043940 buff/cache
KiB Swap: 25165820 total, 18850608 free, 6315212 used. 836564 avail Mem

i have deleted all waiting task and i'll wait tomorrow to see if the scheduled tasks are running as expected.

It seems all devices are bound to core1, this explains why core2 was doing nothing