Repeating Campaign Scheduled in non-ENU Language Stops Running After Two Executions
(Doc ID 3046964.1)
Last updated on SEPTEMBER 30, 2024
Applies to:
Siebel Marketing - Version 23.1 and laterInformation in this document applies to any platform.
Symptoms
After upgrading to 23.1, on the campaigns where repeating execution was scheduled using non-ENU object manager, the campaign was executed successfully on first two days, but the third execution did not happen.
This was visible when navigating to Campaign management -> Campaign list -> drill down on the campaign -> Execute -> Execution status view. On further investigation, it was found that the repeating activity was inactivated after first two executions.
Issue does not happen if the repeating execution is scheduled using the ENU object manager.
This was reproduced internally using FRA object manager and following steps:
1. Navigate to Offers screen and create an offer.
2. Create a treatment of type Phone for the offer.
3. Navigate to Campaign management screen and create a campaign.
4. Go to Design view and associate the offer and the treatment.
5. Navigate to Segments/Lists and add a list with minimum one contact
6. Go to Allocation tab and add 100% percent for the phone treatment. Perform Update count.
Below steps must be performed using FRA callcenter object manager.
7. Navigate to Site map -> Administration des campagnes -> Liste de campagnes
8. Drill down on the campaign created in step 5
9. Select Planning tab and click "+" sign
10. For the activity record created, set:
Type = Campaign Load
Frequence = Daily
Indicateur actif = checked
By default, the load will be scheduled for the next 7 days.
11. Save the record and logout.
12. After 3 days check the campaign execution. Login and navigate to Campaign management -> Campaign list -> drill down on the campaign -> Execute -> Execution status
Notice that campaign was executed twice in the first two days, but the third execution did not happen. The repeating activity was inactivated after first two executions.
Changes
Behavior started after upgrade to 23.1
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |