Content defect: api-composition-supply-risk breaks the PROD content rebuild
Your tutorial tutorials/api-composition-supply-risk/api-composition-supply-risk.md is failing the production content-rebuild pipeline for developers.sap.com. Every push that re-dispatches it fails, and it has now triggered 3 consecutive PROD rebuild failures (auto-escalated in tutorials-ims#2489). Until it's fixed, no content publishes to PROD — the guard aborts the whole run.
What the pipeline sees
The rebuild parsed the tutorial to stepCount: 0 and refused to publish it:
✗ api-composition-supply-risk.md: Invalid 'stepCount' value: 0
[check-approuter-assets] FAILED: no rendered page for slug(s): api-composition-supply-risk
The Hugo build did not emit these pages — the rebuild would publish nothing verifiable.
Failing run: https://github.com/sap-tutorials/tutorials-ims/actions/runs/35890672020
A tutorial that parses to zero steps produces no rendered page, so the pipeline correctly blocks it.
Root cause: malformed frontmatter
The file has a duplicated frontmatter delimiter — two --- lines back-to-back — and non-standard structure placed before the tutorial title:
---
parser: v2
author_name: Shyam
...
primary_tag: software-product>sap-integration-suite
--- ← line 10: closes frontmatter (correct)
--- ← line 11: STRAY second delimiter (remove this)
## Scenario
...
---
# Build a Supply Risk API with API Composition
...
### Step 1 — Set Up the Four Destinations
Two problems:
- Stray
--- on line 11 — the frontmatter block already closes on line 10. The extra --- opens a second (empty) YAML frontmatter block, corrupting how the parser splits frontmatter from body.
- Content before the
# H1 title — the ## Scenario section and scenario image sit above the # Build a Supply Risk API… H1. Canonical SAP tutorials open with the H1 title (and its <!-- description -->), then ## Prerequisites / ## You will learn, then the ### Step N headings. Non-standard pre-title content is a frequent trigger for zero-step parses.
How to fix
- Delete the duplicate
--- on line 11 so the file has exactly one frontmatter block (one opening ---, one closing ---).
- Move the
# Build a Supply Risk API with API Composition H1 to the top of the body (immediately after the closing frontmatter ---), followed by its <!-- description --> line, then ## Prerequisites, ## You will learn, then the scenario content, then the ### Step N headings.
- After editing, confirm the file has 8
### Step N headings and validate locally if you can.
The 8 step headings themselves are well-formed (### Step 1 — … through ### Step 8 — …) — the blocker is the frontmatter/structure above them.
Mirror the fix
If this tutorial also lives in integration-Contribution (the QA/working repo), apply the identical fix there too, or it will drift back on the next promotion.
Filed automatically from the tutorials-ims#2489 PROD rebuild-failure escalation.
Content defect:
api-composition-supply-riskbreaks the PROD content rebuildYour tutorial
tutorials/api-composition-supply-risk/api-composition-supply-risk.mdis failing the production content-rebuild pipeline for developers.sap.com. Every push that re-dispatches it fails, and it has now triggered 3 consecutive PROD rebuild failures (auto-escalated in tutorials-ims#2489). Until it's fixed, no content publishes to PROD — the guard aborts the whole run.What the pipeline sees
The rebuild parsed the tutorial to
stepCount: 0and refused to publish it:Failing run: https://github.com/sap-tutorials/tutorials-ims/actions/runs/35890672020
A tutorial that parses to zero steps produces no rendered page, so the pipeline correctly blocks it.
Root cause: malformed frontmatter
The file has a duplicated frontmatter delimiter — two
---lines back-to-back — and non-standard structure placed before the tutorial title:Two problems:
---on line 11 — the frontmatter block already closes on line 10. The extra---opens a second (empty) YAML frontmatter block, corrupting how the parser splits frontmatter from body.# H1title — the## Scenariosection and scenario image sit above the# Build a Supply Risk API…H1. Canonical SAP tutorials open with the H1 title (and its<!-- description -->), then## Prerequisites/## You will learn, then the### Step Nheadings. Non-standard pre-title content is a frequent trigger for zero-step parses.How to fix
---on line 11 so the file has exactly one frontmatter block (one opening---, one closing---).# Build a Supply Risk API with API CompositionH1 to the top of the body (immediately after the closing frontmatter---), followed by its<!-- description -->line, then## Prerequisites,## You will learn, then the scenario content, then the### Step Nheadings.### Step Nheadings and validate locally if you can.The 8 step headings themselves are well-formed (
### Step 1 — …through### Step 8 — …) — the blocker is the frontmatter/structure above them.Mirror the fix
If this tutorial also lives in
integration-Contribution(the QA/working repo), apply the identical fix there too, or it will drift back on the next promotion.Filed automatically from the tutorials-ims#2489 PROD rebuild-failure escalation.