Hi Din,
The initial problem appears to have been an incorrectly configured action in your model. After resolving that, we discovered there was a server-based configuration issue that one of our devs had to remedy. The latter is not something you would have any control over, as it was an issue with the deployment of the service that hindered integration of the Scheduler and the Content Delivery service (e.g. e-mail templates).
With this feature being relatively new, the issue was something we had not encountered before. Now we are aware of it, we are confident it will not happen for any subsequent Scheduler deployments.
Thank you for your patience, and I'm glad it's now working for you.
Happy building!