Issue with Adobe Target Custom Locations – ODE‑0001‑404 Error

Hi Community,
we are currently experiencing an issue when introducing new Adobe Target locations, while the existing setup is mainly based on the Global Mbox.

At the moment, activities configured on the Global Mbox are correctly evaluated and returned in the response. However, when we attempt to create and use a new dedicated location for more targeted personalization, the Web SDK response consistently returns the following error:

"errors": [

{

"type": "ODE-0001-404",

"detail": "The Decisioning Package was not found."

}

]

On the AEP / Web SDK side, we are following the official documentation available here:
https://experienceleague.adobe.com/en/docs/platform-learn/implement-web-sdk/applications-setup/setup-target
but the error still persists.

From the Adobe Launch side, there is a rule that sends a sendEvent call on page load once the required data is available in the data layer.
In this call:

• personalization parameters derived from the data layer are passed to Target,
• a decisionScope is set with the newly created custom location,
• decision rendering is enabled.

Despite this configuration, the custom location is not correctly resolved by the decisioning engine and the response continues to include the ODE-0001-404 error, while activities associated with the Global Mbox continue to work as expected.

We have also tried aligning with the configuration suggested in the official documentation (including the standard Send Event and rendering setup), but the behavior does not change.

The Datastream is correctly configured and Adobe Target is enabled.

We would like to understand why the usage of custom locations different from the Global Mbox results in the ODE-0001-404 error and whether an additional step is required on the Web SDK / Launch side to properly complete the decisioning lifecycle when introducing custom locations.