I have an active Journey, which was working as expected. Now the emails are not being sent.

The email has ampscript in it, and when I preview this email in the content builder with the target data extension, which is originated from Salesforce data, the email runs with no error.

In the triggered sends from the Journey it shows that the emails have been queued.

My question is:

If an email experience error at the sending and gets stuck in the queue, will the next sends also be queued, even if they were supposed to be send, once there is no error in the ampscript?

1 Answer 1


By default, all the Triggered Sends (with no errors) get queued behind when one of the emails fail (with error) during the send execution.

From my experience, this has been resolved by submitting a Salesforce request to remove the queuing of the TSD sends when an error has occurred during the send execution.

  • No, the emails don't get queued behind failed emails. This is incorrect information.
    – Krati Garg
    Oct 18, 2018 at 6:24
  • If you check the OP's question he hasn't mentioned anything about resolving the AMPscript error. please read the post carefully Oct 18, 2018 at 6:42
  • My answer is based as per the last line, where he has clearly mentioned "once there is no error in the ampscript". And as per your solution, "By default, all the Triggered Sends (with no errors) get queued behind when one of the emails fail (with error) during the send execution." - no this is not how it works. The triggered sends with no errors are not queued. Kindly, re-check.
    – Krati Garg
    Oct 18, 2018 at 6:58
  • Could you please prove it where it says it doesn't @KratiGarg? Oct 18, 2018 at 10:51
  • 2
    my experience is if there is an unhandled error "you didn't invoke the error in the code intentionally" all subsequent emails will be queued, as your triggered send interaction is paused regardless of wether the next email would have had an error or not. In Krati answer he acknowledged that you have to update the email activity in the journey for the sends to restart. This is because the send was paused and updating will restart and resume sends to the queue. This can sometimes be confusing as the triggered send status doesn't always get switched to paused after an error, even though it is. Oct 19, 2018 at 5:25

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .