Environment
Symptoms
Error (If Applicable)
Resolution Summary
Details
Cause
Internal Information
Resolution Category
- Mobile Commons.
- Campaigns.
- Broadcasts.
Symptoms
- When a broadcast gets stuck.
Error (If Applicable)
Resolution Summary
The broadcast was sent successfully after the dev. team restarted the stuck generator.
Details
- The broadcast generators responsible for sending the messages out to the end users may occasionally experience a failure.
- This failure will cause the generator to die and the broadcast will get stuck.
- Unscheduling the broadcast and rescheduling it again will restart the generators which can resolve the issue.
- If the rescheduling didn't work, try to create a new broadcast/ clone the old broadcast if no messages were sent from the one.
- If there are messages sent from the old broadcast and the client needs it to be resumed instead of creating a new one, please create a Jira ticket and flag it to the team.
- If the client needs a reason for the broadcast failure, please create a Jira ticket for the team to investigate the broadcast further.
NOTE: The team is currently looking into implementing an automated Restart feature for the stuck generators to minimize this issue in the future, Details can be found in this Jira ticket
Cause
The generators experienced a failure and caused the broadcast to get stuck.
Internal Information
Example for stuck broadcasts #13313
Resolution Category