Hi APEX team,
we are running into an issue with APEX subscriptions when deploying
applications across environments.
In short:
Subscriptions (shared components and Universal Theme) are getting lost
after import, even though we reuse the same Application ID
and import via the UI.
Environment
-----------
- APEX Product Build: 24.2.14
- Patch Version: 14
- Schema Compatibility: 2024.11.30
- Database: Autonomous Database (ADB)
Deployment is always done in the same way:
- Export application from DEV
- Import via APEX UI
- Reuse the existing Application ID
Infrastructure setup
--------------------
- DEV / QC / UAT:
-
Separate ADBs
-
Same OCI Compartment
- Pre‑Production:
At the APEX application level, everything is the same.
The only difference for Pre‑Prod is that it lives in a different OCI compartment.
Scenario
--------
We have a dedicated master application that contains shared components
(LOVs, Authorization Schemes, including Universal Theme).
Other applications subscribe to those components.
This setup works fine in DEV, QC and UAT.
Problem
-------
After importing the same applications into Pre‑Production,
some subscriptions are broken and show:
"Subscribed From: Nonexistent Master"
This happens even though:
- The master application is imported first
- The same Application ID is reused
- Import is done via the APEX UI
- The exact same process works in DEV / QC / UAT
We see this both with:
- Shared Component subscriptions
- Universal Theme subscription
Workaround
----------
The only workaround we have found is to manually delete
and re‑subscribe the affected components or theme in Pre‑Prod.
Questions
---------
1. Is this expected behavior or a known limitation of APEX subscriptions
when deploying across isolated environments?
2. Is this a known issue or regression in recent APEX versions?
3. Are there any recommended best practices to avoid
"Nonexistent Master" after import, or to rebind subscriptions
in a supported way?
Any guidance would be much appreciated.
Thanks!