Problem

When an APEX application is imported, all scheduled background processes such as Automations, REST Source Synchronizations, and other APEX-managed scheduled jobs are automatically disabled, regardless of their state in the target environment or their state in the source environment as recorded in the export file.

This creates several issues:

1. Inconsistent behavior with other Oracle tools
   For example, when exporting/importing a schema using Data Pump, the default behavior is that Scheduler jobs marked as ENABLED in the dump file start automatically after import.
   APEX scheduled background processes do not follow this expected behavior.
2. Unexpected and non-scalable deployment workflow
   Teams must manually maintain lists of Automations and REST Syncs that were enabled prior to deployment and then re-enable them after import.
   This does not scale for enterprise applications with many scheduled background processes.
3. Surprising for frequent deployment cycles
   Teams typically expect scheduled background processes to return to the same state they were in before installation.
   The current behavior breaks that expectation and requires extra scripting.

Proposed Solution

Export Option (Boolean):

**Start scheduled background processes after import**
Type: Boolean
Default: TRUE

Behavior:
If TRUE, then after importing the application APEX automatically starts all Automations, REST Synchronizations, and other scheduled background processes that were active in the export file.

This simple Boolean option solves ~95% of real-world cases.

Optional Enhancement (List):

Use the same option name, but change the data type to a list:

**Start scheduled background processes after import**

Type: List (3 values)

Possible values:

1. USE_EXPORT_STATE
   Start or stop scheduled background processes based on their state in the export file.
2. PRESERVE_TARGET_STATE
   Keep whatever scheduled background processes were active/inactive in the target environment before import.
3. DISABLE_ALL
   Explicitly disable all scheduled background processes after import.

This extended list-type option supports 100% of use cases, including scenarios where schedules differ between DEV, TEST, and PROD.

Developer Expectation

APEX developers should be able to rely on:

If a scheduled background process was active before installation, it should remain active afterward — unless explicitly overridden via configuration.

No workaround scripts or manual tracking lists should be required.

Reference

Forum discussion with more details:
https://forums.oracle.com/ords/apexds/post/automations-and-rest-sync-are-disabled-after-import-2801