Is it possible to configure different Cron schedule for multiple batch audiences in AEP?

[ShashiCh]

Looking for options if we can configure different CRON schedule for different batch audiences (Lets assume custom schedule is always more than 24 hours). When below request was sent to create a schedule for a specific audience, it is throwing error response as below. If there is not such capability, it is good feature to have from Adobe in upcoming releases as not all batch audiences required to run every 24 hours (which increases the load on the system).

code": "UPAPI-054606-400",

"message": "There is a problem in chronos schedule validation. Reason - You can only schedule the job at most once a day

Request 

{

    "name":"custom-segment-schedule",

    "type":"batch_segmentation",

    "properties":{

        "segments":[

            "0d941a41-4254-4de4-8ca9-695c861bf942"

        ]

    },

    "schedule":"0 15 6 10 * ? ",

    "state":"inactive"

}

Response

 "errors": {

        "400": [

            {

                "code": "UPAPI-054606-400",

                "message": "There is a problem in chronos schedule validation. Reason - You can only schedule the job at most once a day."

            }

        ]

    },

[brekrut · Accepted solution]

Hello @ShashiCh  

You can only configure 1 batch segmentation scheduler within the Adobe RTCDP platform.  Is the requirement to evaluate or activate segments on a different interval.

Segments can be activated to destination at different intervals. 

[ShashiCh]

@brekrut

We are creating bunch of helper audiences which are not mean to be evaluated daily but once a month. So you can reduce the load on the system daily.

[brekrut]

can you give more context of a helper audience and how this is different than a target audience?

[ShashiCh]

1. We are building a journey which could run once a month.

2. Helper audience is basically combo of Audience Rules + Journey Condition Rules, but this is not a target audience which could trigger the journey.

3. Helper audience is also essential in pulling specific profiles and do data manipulation through Data disteller query through which specific attribute in the profile gets updated. This helper audience was created to avoid adding all the journey conditions in the scheduled data disteller query. (We cannot remove journey condition and put them in target audience because of quick live report needs).

So we see that helper audience is not required to run daily because journey triggers once a month.

Irrespective of the context or use cases, If a journey runs once a month/weekly/yearly through read batch audience mode, It is not required to run the segmentation job daily for that batch audience unnecessarily. As you know, when number of audiences increases, job segmentation completion time also increases. It is a good feature if we could configure the schedule in audience UI and run batch audiences (> 24 hours) at our will. By default system runs the job 24 hours, but we should be to override them to run at different schedules (definitely not within 24hours)