To replay to Hartmut, Rik and Gaurav,
I agree with you. I have no reason to suspend the task, but, instead, it is better to wait the next message.
The task was originally designed to do one job after a reset, if some conditions are true. Then its purpose is finished.
With the evolution of the application, the same job can be done not only after a reset, but also when there are specific events. The idea was to keep the task suspended just as an extra precaution, to avoid side effect if other application tasks, out of my control, send commands to Task_A by mistake.
Thanks for you answer,
Stefano