If you don't catch the error the Scheduled Event won't run again untill the next restart. That's probably why you are not able to debug it now.
You could create a temporary button, calling the same mf, for debugging purpose.
Your scheduled event did start, but it has an error. If it's data dependent, that would explain why it works locally, but not in the cloud.
Your scheduled event is being triggered but as stated the microflow that is started has an error in the eval of an expression. Connect the debugger to your environment to check what the exact issue is when the scheduled event is triggered.
See https://docs.mendix.com/howto/monitoring-troubleshooting/debug-microflows-remotely for more information on how to debug your cloud environment remotely.