Hi,
Thank you for your reply.
I checked the task contents and didn't found any suspicious configuration, also I configured a similar task with yours belong to your configuration, it shows the same action result with you.
So I think the behavior is caused by some threads which caused the computer unable to get into idle. If we want to troubleshoot further deep, we could use process monitor tool to monitor thread actions before computer shutdown and task triggered.
As the task is waiting for computer idle status instead of force computer to shutdown, so I think it would has a more flexible time than a specific time to force shutdown. So that, we think we could ignore the behavior.
Bests,
============================================
If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.