Skip to main content

Invoking a fallback strategy

Suggest edit
Updated on January 19, 2022

If a Strategy execution fails due to an exception, Pega Customer Decision Hub invokes a fallback Strategy. The fallback Strategy results in a response when a service activity is executed. To configure the required action data, save the strategy FallbackStrategy into your implementation layer.

Pega Customer Decision Hub

When your Container Service exceeds the Service Level Agreement defined for the Container Service by more than a specified number of consecutive violations, Pega Customer Decision Hub invokes a fallback service activity instead of the default service activity. The fallback service activity returns the default set of actions for every request. To change the set of actions, save the FallBackContainerResponse data transform into your implementation layer and configure the default Container Service response.

A sample response from the invocation of this service is shown below:

For example:
"ContainerList": [
        {   "Status": "OK",
            "ContainerName": " TopOffers ",
            "RankedResults": [
                {
                    "Group": "Default",
                    "Issue": "Fallback",
                    "InteractionID": "-8654833423861133119",
                    "Category": "Category",
                    "CustomerCost": "0",
                    "WhyRelevant": "WhyRelevant",
                    "Benefits": "Benefits",
                    "Direction": "Direction",
                    "Name": "FallbackOffer",
                    "ShortDescription": "ShortDescription",
                    "PaidAudienceName": "PaidAudienceName",
                    "Identifier": "Identifier",
                    "Pricing": "Pricing",
                    "JourneyStage": "JourneyStage",
                    "JourneyStep": "JourneyStep",
                    "EligibilityDescription": "EligibilityDescription",
                    "Propensity": "0",
                    "AgentCompensation": "0",
                    "Priority": "0",
                    "ClassIdentifier": "Offer",
                    "Channel": "Channel",
                    "ImageURL": "ImageURL",
                    "Rank": "1",
                    "BundleParent": "BundleParent",
                    "Variant": "Variant",
                    "Treatment": "Treatment",
                    "InternalCost": "0",
                    "CampaignID": "CampaignID",
                    "OfferValue": "0",
                    "ClickThroughURL": "ClickThroughURL",
                    "Journey": "Journey"
                }
            ]
        } ]
  • Previous topic Configuring a container invocation script
  • Next topic Identifying customers who interact with a real-time container
Did you find this content helpful? YesNo

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us