gCTS in S/4HANA Cloud 2502: “Could Not Verify Content” / “Registered Commits couldn’t be read” Error

[dnnunes]

Hello SAP Community,

I’m in a multi-off delivery scenario, where I develop ABAP custom code in an SAP S/4HANA Cloud 1-system environment (the source) and then deploy it to an SAP S/4HANA Cloud 3-system environment (the target) using Git-Enabled CTS (gCTS). Concretely, I push commits from the 1-system landscape to a remote Git repository, and then attempt to pull those commits into the 3-system landscape (DEV → TEST → PROD).

Since the S/4HANA Cloud Public 2502 upgrade in our 3-system TEST environment, I can no longer import new commits from my remote Git repositories using Git-Enabled CTS (gCTS). Each time I try to pull a commit, I see:

Could not verify content
The repository was not imported because the content could not be verified. Please contact the repository owner.

And in the technical details:

Error action COMMIT_VERIFICATION Code 411x011: Registered Commits couldn’t be read.

In the gCTS logs (the ones viewable in the gCTS Fiori application), I mostly get “Error when importing commit” without much else. However, looking deeper into the Eclipse ADT Feed, Gateway error logs (OData service SCTS_GCTS_SRV) reveals more specific messages, such as:

{... ,"section": "REPOSITORY", "action": "PULL_BY_COMMIT", "severity": "ERROR", "message": "BAdI 'scts_gcts_enh_deploy' raised exception for 'check_before_import' "}

{"severity":"ERROR", "message": "Error when importing commit.", "code": "GCTS.API.411"}

It seems the COMMIT_VERIFICATION step fails before the import actually begins. This problem started immediately after the 2502 upgrade — previously we had no issues pulling from the same Git repository.

Has anyone seen this error in a multi-off delivery scenario?

• Is there a new verification check in 2502 that might fail if certain commit data, authorizations, or repository settings aren’t in place?
• Could the BAdI scts_gcts_enh_deploy be blocking the import for some reason in check_before_import?
• Are there SAP Notes/KBAs covering a similar error in COMMIT_VERIFICATION with “GCTS.API.411” or “Registered Commits couldn’t be read”?

Environment/Versions

• Source: S/4HANA Cloud Public 1SL (Partner Demo) – version 2408
• Target: S/4HANA Cloud Public 3SL (DEV → TEST → PROD) – Currently failing in TEST version 2502. DEV is still in version 2408, commits are being pulled successfully.
• gCTS for multi-off delivery with a GitHub remote repository

I would appreciate any pointers or workarounds for getting multi-off delivery working again in 2502.

Thank you in advance!