You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the problem is with email activities in journeys: journey builder's API only shows the first triggeredSend that was created for it and later iterations, even across journey versions, do not find their details getting updated in the journey metadata.
that combined with the inability to retrieve CC/BCC details from the TriggeredSendDefinition SOAP object is a problem for deployments. Therefore, one should always deploy journeys and drop this info. The easiest is to do this when deploying with templates.
The text was updated successfully, but these errors were encountered:
the problem is with email activities in journeys: journey builder's API only shows the first triggeredSend that was created for it and later iterations, even across journey versions, do not find their details getting updated in the journey metadata.
that combined with the inability to retrieve CC/BCC details from the TriggeredSendDefinition SOAP object is a problem for deployments. Therefore, one should always deploy journeys and drop this info. The easiest is to do this when deploying with templates.
The text was updated successfully, but these errors were encountered: