benecaster_migration_failed_send_retried
Fires after a podcaster clicks Send again on a failed welcome email in the migration dashboard’s Emails that did not send panel, and that email has been put back in the queue.
This is not a resend, and nothing is recorded against the person. The welcome never arrived, so sending it now does not count as chasing them: their next reminder still goes out on schedule and their resend count does not change. That is the opposite of benecaster_migration_invite_resent. A callback that treats this as a chase, or reads the person’s record expecting a new date on it, gets it wrong.
It fires after the email is queued, not after it is delivered. Sending is paced, so it may leave minutes later, or fail again and reappear in the panel. Only a failed welcome to somebody still mid-move can be sent again; every other refusal writes nothing and fires nothing.
Parameters
| Name | Type | Default | Description |
|---|---|---|---|
$queue_id |
int |
— | ID of the email's row in Benecaster's email queue |
$import_id |
int |
— | ID of the import the email belongs to |
$show_id |
int |
— | ID of the show the import belongs to |
Need this built rather than just documented? See our services →