SDO timeout message after SDO request was successful

[KreideGit]

Describe the bug
A SDO timeout message appears on the bus even though the SDO request has completed successfully.

To Reproduce
Start a SDO Upload request (SDO state is busy) with a timeout of 1000ms.
SDO request finishes (SDO state is idle).
Start a new SDO Upload request (SDO state is busy again).
Because the timer of the first request is not deleted it runs out and calls the callback function.
The callback function checks if the SDO state is busy (which it is because of the second request which is still in progress).
The callback function thus sends a timeout message.

Expected behavior
The callback function shall not send a timeout message.

CANopen Stack (please complete the following information):

• Device: [Virtual Machine]
• OS: [Linux Debian x64]
• Version [12 (Bookworm)]

This bug happens consistently because my AppClock timer matches the period of the SDO timeout and I start a new SDO request each AppClock update.