Skip to content

Update deployment-logs-and-limitations.md #11816

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
pedrokuhn wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update deployment-logs-and-limitations.md #11816

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions docs/continuous-delivery/manage-deployments/deployment-logs-and-limitations.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -68,3 +68,8 @@ To work effectively with log display behavior:
* Consider breaking down steps that generate excessive logs into smaller tasks
* Add identifiers or markers to log lines to make them easily searchable
* If you notice missing logs during real-time monitoring, refresh the page after step completion to view the full output

## Pipeline YAML size limitation
Harness enforces a hard limit on the total rendered pipeline YAML size of 3MB (3,145,728 code points). This includes all referenced templates and nested templates/groups. If a pipeline exceeds this limit, execution may not start.
Recommended mitigations include reducing nested template complexity and moving large inline scripts to File Store.
For details and troubleshooting steps, go to [The incoming YAML document exceeds the limit: 3145728 code points](/docs/troubleshooting/troubleshooting-nextgen/#the-incoming-yaml-document-exceeds-the-limit-3145728-code-points).