"Sleep" is defined as ultra-low power usage: All subsystems get turned off and consume extremely little power but can be woken up quite quickly by an external event: lid open, power button, key press, WOL packet, BIOS.
So no, your command will not be running in "sleep" mode, but can run in low-power mode: in that mode, your disk turns off if not needed any more and the same goes for the screen, keyboard, ... but WiFi, LAN, memory, CPU, ... just keep churning away.
Alternatively, you can:
- Send WOL packets by one server that never sleeps and will "wake up" (even from hibernation or completely turned off) other machines that are allowed to sleep. (like the nightwatchmen that will wake up the full Royal Guard)
- If your BIOS supports this feature: Have the BIOS wake up your machine at a specific point in time. (another example of an external wakeup)