Customers with large or complicated property or include rules can use that parameter to speed up the activation request.
Enabling this parameter delays time-consuming validations that ordinarily result in a direct error response so that any errors appear later once you open the
activationLink or run “Get a property activation” or “Get an include activation”. In that case, the activation’s status is
Let’s take a closer look at what PAPI does behind the scenes each time you activate a property or include. This will help us understand the benefit of delaying validations better.
When activating a property or include in a standard way, PAPI performs a few time-consuming validations before submitting the new configuration to Akamai’s Content Delivery Network (CDN).
Potentially upgrades JSON rules to the latest software release.
Checks JSON rules for errors.
Checks warnings against the list of provided acknowledged warnings.
Generates XML from JSON rules.
Runs validations on XML.
Submits the XML to the downstream system for activation.
activationIdprovided by the downstream system.
delayValidations=true, PAPI performs only a minimal validation of the request
before it returns an
activationId. PAPI constructs its own
activationIdinstead of forwarding the one obtained from the downstream system.
PAPI only performs the remaining validation steps after the request is complete. All validations are performed the same way as previously, but they no longer hold up the activation request. The original HTTP request will take less time because it finishes before the validations start.
As with any activation, you should poll the
activationId by running the “Get a property activation” or “Get an include activation” operations until the
status is either
For some failures, you’ll need to wait for the remaining validations to complete to learn the root cause.
If you’re experiencing 500 errors due to timeouts when activating your properties or includes or they take significant time to activate, you should set
true in your requests.