When a task uses an automated email workflow, a customer may occasionally report that they did not receive the email, or you may suspect that the email was not sent successfully. ProgressionLIVE provides tools that allow you to verify whether the email was sent and review any delivery errors.
Step 1 – Review the Task History
Open the affected task in the Web interface.
Open the task.
Go to the History tab.
Review the Event Log section at the bottom of the window.
The Event Log records all actions performed on the task, including automated email deliveries.
If the Email Was Sent Successfully
You may see a message similar to:
Email sent to: user@example.com
or
Email sent to user@example.com received
This confirms that the automation was triggered and that the email was sent.
If the Email Was Not Sent
You may see a message similar to:
Email not sent to: user@example.com
By expanding the entry using the + symbol, you can view the detailed error returned by the email server.
Common errors include:
Mailbox full
Invalid or non-existent email address
Delivery rejected by the recipient’s mail server
Email blocked as spam
Temporary delivery failure
If one of these errors occurs, verify the recipient’s email address and email configuration.
Tip: If the error message is unclear, contact ProgressionLIVE Support for assistance in determining the root cause.
Example of the Event Log
image-1
Step 2 – Verify That the Automation Was Triggered
If no email-related entry appears in the Event Log, the automation may not have executed.
To verify the automation:
Open the Management menu.
Select Automation from the left menu.
Open the My Automations tab.
Locate the automation responsible for sending the email.
You can sort automations by Type to quickly find entries of type Automated Email Sending.
Once located:
Click Edit (pencil icon).
Verify the task type associated with the automation.
Verify the Progress to Status setting.
This setting determines exactly when the email is sent.
Make sure that:
The task matches the configured task type.
The task reached the configured status.
The automation is enabled.
Example of the Automation List
image-2
Special Case: “rejected: general” Error
You may occasionally encounter the following error:
rejected: general
This usually indicates that a previous email delivery failure caused the address to be blocked by the system to prevent repeated failed delivery attempts.
If this error appears:
Contact ProgressionLIVE Support.
We will review the original error that caused the block.
Once the issue is resolved, the email address can be unblocked if required.
What If You Cannot Find the Automation?
Some organizations still use a legacy email automation system configured directly by the ProgressionLIVE team.
If you cannot find an automation that should be sending emails:
Contact ProgressionLIVE Support.
We will verify whether the legacy system is being used.
We will validate that the configuration is still functioning correctly.
Summary
To verify an automated email delivery:
Open the task and review the Event Log.
Look for a sent or failed email entry.
Review any available error details.
If no email activity exists, review the associated automation.
Verify the task type and triggering status.
Contact Support if the error is unclear or if you encounter a rejected: general message.