We’re having significant issues with our supplier collaboration workflow where email notifications are simply not being sent. The workflow is designed to notify external suppliers when they’re added to change orders or when documents require their review, but suppliers report they’re not receiving any emails.
The workflow notification setup appears correct in the admin console - we’ve configured notification rules for supplier user profiles with the appropriate triggers (supplier added, document shared, approval required). The workflow executes without errors and shows notification steps as completed in the workflow history, but no emails are actually delivered.
We’ve verified SMTP connectivity by sending test emails from the Agile admin console, which work fine. However, the workflow-generated notifications specifically for supplier collaboration don’t go through. This is severely impacting our supplier onboarding process and causing delays in getting external feedback on design changes.
Our supplier user profile validation shows active accounts with valid email addresses. We’ve checked spam folders and confirmed with suppliers that they’re not blocking our domain. The notification queue in Agile shows messages as sent, but suppliers never receive them. What could cause workflow notifications to appear successful but not actually deliver emails?
Don’t overlook the notification queue processing. Even if notifications are queued, the notification processor service might not be running or might be configured to skip external addresses. Check the notification service status in the admin console under System Settings > Services. Also review notification processor logs for any filtering or rejection messages related to supplier email addresses.
Check if your supplier users are configured as external users versus internal users. Agile has different notification routing for external collaborators. Also verify that the notification templates include the supplier’s email field, not just the username. Sometimes workflow notifications use internal routing that doesn’t work for external addresses.
Interesting point about external user configuration. Our suppliers are set up as Supplier users in Agile with external email addresses. The notification templates do reference the email field correctly. Could there be a setting that specifically enables or disables external email delivery for workflow notifications?
Yes, there’s a property in agile.properties that controls external email delivery: notification.external.enabled=true. If this is set to false or missing, workflow notifications only go to internal users. Also check notification.external.domains - if configured, only emails to listed domains will be sent. This is a security feature to prevent accidental disclosure to unauthorized external parties.