SSJS script activity fail to create Triggered send definition despite successful run.
Last updated 2021-10-26 ·Reference W-9991523 ·Reported By 1 users
In Review
Summary
While utilizing SSJS script activity within the Automation Studio, the run was successful but the Triggered send definition was not created.The same SSJS code is working fine on a CloudPage JS Code resource page.
Repro
Sample code:
<script runat="server">
Platform.Load('Core', '1.1') try{
var prox = new Script.Util.WSProxy();
// var guid = Platform.Function.GUID();
// var name = "my test TS"; var tsdef = {
Name: "my test TS",
CustomerKey: "my test TS",
SendClassification: {
CustomerKey: "Default Transactional"
},
Email: {
ID: 365255
},
List: {
ID: 299424
},
SendSourceDataExtension: {
CustomerKey: "Test_ TriggeredSendDataExtension"
},
TriggeredSendStatus: "New",
AutoAddSubscribers: true,
AutoUpdateSubscribers: true
} var res = prox.createItem("TriggeredSendDefinition", tsdef);
} catch (e) {
var err = "Trigger Not created";
Write(Stringify(e));}</script>
Workaround
No workaround at the moment.
Reported By (1)
Is it Fixed?
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.
