Viren Adiyecha
Hello,
I have created a subscription using rest API but when I trigger this subscription, I am not receiving email notification. Even the other recipients who are subscribed to this subscription are receiving the notification. Only the owner is not receiving notification.
I am using below payload:
{
"name": "Test Subscription",
"description": "",
"form": {
"id": "cab9004d-259a-40dc-9fe8-81ea7e32d6a6"
},
"owner": {
"id": "1931ddd3-aaf4-4e83-9a63-a9a09371653e"
},
"notificationDelay": 0,
"criteria": [
{
"name": "markets",
"operator": "IS_ONE_OR_MORE_OF",
"values": [
"AB",
"AL",
"AR",
"AT"
]
},
{
"name": "priority",
"operator": "IS_ONE_OR_MORE_OF",
"values": [
"P2",
"P3"
]
},
{
"name": "services",
"operator": "IS_ONE_OR_MORE_OF",
"values": [
"1",
"2",
"3",
"4",
"5"
]
}
],
"recipients": [
{
"id": "1931ddd3-aaf4-4e83-9a63-a9a09371653e"
}
],
"targetDeviceNames": [
{
"name": "Alternate Email"
},
{
"name": "Android Phone"
},
{
"name": "Android Tablet"
},
{
"name": "iPad"
},
{
"name": "iPhone"
},
{
"name": "SMS Phone"
},
{
"name": "Work Email"
}
]
}
Is there anything I need to pass along with the request?
0
Comments
Please sign in to leave a comment.
Hey Viren,
That's interesting. I think your payload looks ok. Can you post the properties of the event from the Reports > (event) > properties. We should make sure the services, priority and markets matches with the event.
I suppose the other thing to check is the owner's devices. Do they have at least one of the devices you have listed? And are those devices "on-call"?
Happy Friday!
--- Travis
Hi Viren,
I tried poking around and did not see this subscription listed at the moment. It may be we need to work on this more directly but have you considered checking the event's logs to see if you are targeted for notification at all? And if you are is there a log entry for your e-mail to be notified? If you are in the list of subscribers and your person (not your device) is subscribed there generally it should just work. Whether you create the event or the subscription should have no bearing on how you get notified.
Let me know if we need to dig into this further with a support ticket and I'll get one rolling for us.
Hi Viren,
Thanks for submitting the issue, and providing so much detail so Francois could forward to our engineering team. Our API team took a look and was able to recreate the issue very quickly, thanks to the detail you provided. They determined it was a defect in how the subscription was created that prevented it from being considered during the notification process.
A fix was deployed last week, in release 262, that should address this specific problem. Sorry for any inconvenience it may have caused. When you have time, please verify that it's working as expected and let us know if it is not so we can investigate further.
Thanks,
Craig