I am looking for a solution to avoid this scenario.
We had a deployment issue on of our client account, the message was scheduled to throttle 1000/day over 9 days, but it stopped after 5 days because the default delivery duration expired at 5 days.
can I get some help to set up a notification in ACS which would let me know when throttling and expiry periods might conflict?
what are the other possible recommendations to avoid such issues.
appreciate your help.
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
can someone please help ?
Views
Replies
Total Likes
please advise.
Views
Replies
Total Likes
@MANDM123 Can you tell me how you're setting up throttling if it's supposed to be 9 days in this case?
Views
Replies
Total Likes
in our case the throttle was set to 500 messages/day for a period of 9 days, however as the default delivery duration is set to 5 days the delivery stopped after 5 days.
also the delivery does not go into a failed state where the delivery alerting would help as advised by you earlier.
since it expired and (The delivery has expired; status changed automatically (by the clean-up task).
we understand that there would be manual checks whenever were are creating such throttling to ensure the validity period is adjusted as per the throttle, but there are chances we may miss, so we want something that atleast notifies us if a delivery is conflicting with the throttling set up or nearing expiry.
Views
Replies
Total Likes
Ok, I understand that we can't achieve this through a delivery alerting report. But the default delivery duration max is 3.5days.
Views
Replies
Total Likes
Views
Replies
Total Likes
Views
Replies
Total Likes
can you please explain me how the delivery alerting report would help me to get notified for the below scenario.
can I get some help to set up a notification in ACS which would let me know when throttling and expiry periods might conflict?
Views
Replies
Total Likes
Views
Likes
Replies