3804104 - [RESOLVED] Replication flows fail with 'tenant pool is in boot strapping' in SAP Datasphere

• Replication Flows fail to start with the error: "add tenant the id failed: tenant pool is in boot strapping"
• Replication flow creation is not possible as fails with: Failed to create RMS target space , tenant pool is in boot strapping

•  SAP Datasphere

1. Start a run of a Replication Flow.
2. Observe the run fails with the error "add tenant the id failed: tenant pool is in boot strapping" and the status remains "Running (Retrying Objects)".

or

1. Create a new replication flow
2. Deploy it and fails with Failed to create RMS target space , tenant pool is in boot strapping

• The tenant pool is in "boot strapping" (temporary initialization) state.
• Datasphere product issue

2026-09-09 01:50 UTC

• Fix has been applied to the landscape.
• Development team has put in monitors to observe and prevent this issue in the future.

2026-09-08 19:00 UTC

• Development team is working to identify the root cause and provide a fix
• Subscribe to this KBA for further information about the ongoing solution.

replication flow, tenant pool is in boot strapping, add tenant failed, running retrying objects, paused run, a user paused the run, datasphere replication flows, abap cds source, replication flow runtime, bootstrapping, paused status, start run failure, retrying objects , KBA , DS-DI-RF , Replication Flow Runtime , CA-DI-CP-SM , System Management , DS-DI-ABA , Datasphere - Data Flow / Replication Flow ABAP Integration , Problem