@kapa.ai pipelines stop working as it should 2026-09-05 051630 platform INFO ----- START POST REPLICATION OPERATIONS ----- 2026-09-05 051630 platform INFO No post-replication operation(s) to perform. 2026-09-05 051630 platform INFO ----- END POST REPLICATION OPERATIONS -----

Thinking completed I'm sorry, but the provided log snippet alone does not contain enough information to determine why the pipeline stopped working. The lines:

----- START POST REPLICATION OPERATIONS -----
No post-replication operation(s) to perform.
----- END POST REPLICATION OPERATIONS -----

are a standard cleanup step executed at the end of a replication attempt, regardless of whether it succeeded, failed, or was aborted [Github Issue (closed): [destination-mssql] no exit code issue; Github Issue (open): Replication pod creation fails (KubeClientException) but UI/Public API still reports sync as successful]. In similar reported issues, the actual root cause typically appears directly before or around this block in the platform logs, often during the pipeline execution stages [Github Issue (open): Socket-based syncs blocked by AKS ContainerNoPrivilegeEscalation Policy; Github Issue (open): Replication pod creation fails (KubeClientException) but UI/Public API still reports sync as successful]. Common causes include: • Resource constraints:

ResourceConstraintException: Unable to start the REPLICATION pod. This may be due to insufficient system resources

(e.g., lack of CPU/memory on the Kubernetes cluster) [Github Issue (open): S3 Datalake Connector: Failures marked as success. Main branch never created.; Github Issue (closed): Airbyte MSSQL → MSSQL: Tables are created but no data is replicated (0 rows) – silent behavior with non-dbo schema and Full Refresh]. • Pod creation or policy failures:

KubeClientException: Failed to create pod

(for example, caused by cluster security policies such as

ContainerNoPrivilegeEscalation

) [Github Issue (open): Socket-based syncs blocked by AKS ContainerNoPrivilegeEscalation Policy; Github Issue (open): Replication pod creation fails (KubeClientException) but UI/Public API still reports sync as successful]. • Init container failures:

Init container for Pod: pods did not complete successfully

[Github Issue (open): Replication pod creation fails (KubeClientException) but UI/Public API still reports sync as successful]. • Connector or destination errors: Failures such as

Destination process exited with non-zero exit code

[Github Issue (closed): replication-orchestrator ERROR]. Next Steps Please check the logs immediately preceding this section (or in the connector/orchestrator pods) for lines containing

ERROR

,

Stage Pipeline Exception

, or

Pipeline aborted after error

to find the specific error message [Github Issue (open): Socket-based syncs blocked by AKS ContainerNoPrivilegeEscalation Policy; Github Issue (open): Replication pod creation fails (KubeClientException) but UI/Public API still reports sync as successful]. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.