Frequently Asked Questions FAQ
Are there any restrictions on sending messages if start events occur repeatedly?
Yes, it depends on the resending option when setting up the campaign. If one-time sending is allowed, it will be sent once within the period, and if multiple sending is set, it will be sent multiple times even if duplicate events occur within the period.
At the end of the campaign period, what happens to messages that were waiting but could not be sent?
The message will not be sent.
What happens when a message that has expired is caught in Do Not Disturb?
It works differently depending on your Do Not Disturb settings. If you set it to 'Skip', the message will not be sent, and if you set it to 'Send after Do Not Disturb', it will be sent after the Do Not Disturb time.
What happens when a termination event occurs while a message is waiting to be sent according to the ‘Send after Do Not Disturb’ setting?
When an end event occurs during the Do Not Disturb time period will depend on the wait time you set.
대기 시간 내 종료 이벤트 발생시메시지가 발송 되지 않습니다.
대기 시간 후 종료 이벤트 발생시 대기 시간이 지난 후 종료 이벤트가 발생되었으므로, 발송 대기 시간만 지나면 메시지가 발송됩니다.
If the user fires a start event 5 times and the wait time is set to 1 day, how are exception events handled when they occur?
Delete all delayed messages.
Are there any restrictions on the operating period?
Yes, there is.
Restrictions
Sending typeOperating period restrictionsOne time delivery
• Cannot be sent within 1 hour of campaign setting date and time
• Can be set within 100 days from current standard
• Fixed to service time zone
Trigger dispatch
• Cannot be sent within 1 hour of the campaign setting date
• Cannot set the start date to be more than 100 days after the campaign setting date
• Cannot set the period range to exceed 100 days
• Cannot set the period range to within 1 hour
• Fixed to the service time zone
Last updated