Removed outdated recommendation

[AlexejPenner]

Describe changes

I implemented/fixed _ to achieve _.

Pre-requisites

Please ensure you have done the following:

• I have read the CONTRIBUTING.md document.
• I have added tests to cover my changes.
• I have based my new branch on develop and the open PR is targeting develop. If your branch wasn't based on develop read Contribution guide on rebasing branch to develop.
• IMPORTANT: I made sure that my changes are reflected properly in the following resources:
  • ZenML Docs
  • Dashboard: Needs to be communicated to the frontend team.
  • Templates: Might need adjustments (that are not reflected in the template tests) in case of non-breaking changes and deprecations.
  • Projects: Depending on the version dependencies, different projects might get affected.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Other (add details above)

[github-actions]

🔍 Broken Links Report

Summary

• 📁 Files with broken links: 1
• 🔗 Total broken links: 1
• 📄 Broken markdown links: 1
• 🖼️ Broken image links: 0
• ⚠️ Broken reference placeholders: 0

Details

File	Link Type	Link Text	Broken Path
steps-pipelines/advanced_features.md	📄	"dynamic pipelines"	../dynamic_pipelines.md

📂 Full file paths

• /home/runner/work/zenml/zenml/scripts/../docs/book/how-to/steps-pipelines/advanced_features.md

[github-actions]

Documentation Link Check Results

❌ Absolute links check failed
There are broken absolute links in the documentation. See workflow logs for details
❌ Relative links check failed
There are broken relative links in the documentation. See workflow logs for details
_{Last checked: 2025-12-03 22:43:47 UTC}

[schustmi]

Dynamic pipelines is still experimental, I wouldn't recommend them to anyone yet. But even once they're ready, don't you think it makes sense to keep the code sample on how to do it with static pipelines as well, just for the users that want to/must use static pipelines for some reason or another?

We can make the fan-in much nicer now even, as in static pipelines we also allow list of input artifacts, which gets rid of this whole code in the combine step. The only real limitation of static pipelines is the fan-out amount is fixed, but in some cases this might not even be a problem for users.