How to fix it

  1. Navigate to System Policy > Email > Inbound Actions and locate your inbound action.
  2. Verify the Active field is checked (true). If not, activate it and test.
  3. Open the sys_email table and find your received email by searching for the sender or subject.
  4. Compare the From, To, and Subject values in the sys_email record against your inbound action conditions.
  5. If conditions don't match, update your inbound action filters. Use contains operator instead of is for more flexible matching.
  6. Check System Mailboxes > POP3/IMAP Account to verify your email polling account is active and not showing connection errors.
  7. Navigate to System Policy > Email > Inbound Actions and sort by Order field (ascending) to see processing sequence.
  8. Look for other active actions with lower order numbers that might be intercepting your emails and have Stop processing checked.
  9. Check System Logs > Script Errors for any JavaScript errors in your inbound action script around the time the email was received.
  10. If script errors exist, fix the JavaScript code in your inbound action's Script field and save.
  11. Test by sending another email to your inbound address and monitoring the sys_email table for the new entry.
💡

Enable debug logging for inbound email processing by setting the log level for 'com.glide.communications.email' to 'debug' in System Logs > Log Levels to see detailed processing information.