Your notification failure is a common post-migration issue that requires systematic resolution across multiple configuration areas.
Analyzing your three key symptoms:
No notifications sent post-cloud move: Cloud environments don’t automatically inherit on-premise email infrastructure. Your on-premise deployment likely used your organization’s internal SMTP server for email delivery, which was configured at the network level. Cloud deployments require explicit email delivery service configuration within Workday because they operate in isolated cloud infrastructure without access to your internal mail servers.
Business process includes notification steps: The business process configuration itself is intact and executing correctly. The notification steps are triggering as designed, but the actual email delivery mechanism is missing. Think of it like a notification being created and addressed but having no postal service to deliver it.
No errors in logs: This is the confusing part - Workday logs show successful business process completion because from the process perspective, everything worked. The notification was generated, queued, and handed off to the (non-existent) delivery service. The absence of a delivery service doesn’t generate an error in the business process logs because the handoff completed successfully.
Complete resolution framework:
Phase 1 - Configure Cloud Email Delivery Service:
- Navigate to Integration System > Email Delivery Configuration
- Select “Configure Workday Cloud Email Service”
- Enable the service and set Status = Active
- Configure sender email address (use a monitored address like workday-notifications@yourcompany.com)
- Set as Default Delivery Service for all notification types
- Save and verify activation
Phase 2 - Update Notification Templates:
- Navigate to Notifications > Notification Templates
- Search for work order related templates (filter by “Maintenance” or “Work Order”)
- For each template:
- Verify Status = Active
- Click Edit
- In Delivery Channels section, select “Email”
- Assign “Workday Cloud Email Service” as the delivery service
- Verify recipient configuration (should include role or position)
- Save changes
Phase 3 - Validate Business Process Integration:
- Open your Maintenance Work Order business process
- Review each notification step
- Verify that notification steps reference the correct templates
- Check that conditional logic (if any) isn’t preventing notification triggers
- Ensure notification steps occur after data commit steps
Phase 4 - Test End-to-End Delivery:
- Create a test work order as a technician
- Monitor business process execution in Process History
- Check Notification History to verify notification generation
- Confirm email delivery to supervisor inbox
- Test status change notifications by updating work order status
Critical cloud-specific considerations:
Cloud email delivery has rate limiting and throttling policies. If you have high-volume work order creation, configure batch notification settings to group multiple notifications into digest emails rather than individual messages. This prevents delivery delays during peak usage.
Also review your notification recipient configuration. Cloud deployments are stricter about valid email addresses. If worker records have invalid or missing email addresses, those notifications will fail silently. Run a report of all facility workers and verify email address completeness.
Addressing the maintenance delay impact:
For your immediate backlog, create a custom report showing all work orders created since migration with Status = Open or Pending. Distribute this to supervisors manually while the notification system is being restored. Also consider temporarily enabling in-app notifications as a backup channel - these work independently of email delivery configuration.
Once email delivery is configured, notifications for future work orders will trigger automatically. Historical work orders won’t retroactively send notifications, so you’ll need to manually communicate the backlog to your maintenance supervisors.
The lack of errors in logs is actually working as designed - Workday distinguishes between business process execution errors and delivery service errors. Enable email delivery logging separately under Integration System > Email Delivery Logs to track actual delivery success/failure rates going forward.
This draft is based on general Workday knowledge. It has not been verified against your specific version and environment. Practitioners: verify the steps and share your experience below.