-
Notifications
You must be signed in to change notification settings - Fork 1
Large Response and Diagram Handling
Aryeh Citron edited this page May 1, 2026
·
4 revisions
Note: This page covers diagram splitting — when a diagram has too many interactions to fit in a single image. For truncating or redacting content within individual diagram notes (wide tokens, large bodies, sensitive data), see Filtering and Redacting Diagram Content.
The library automatically handles large content using three splitting mechanisms:
| Trigger | Threshold | What it does |
|---|---|---|
| Encoded PlantUML length | 2,000 characters (DefaultMaxEncodedDiagramLength) |
When the URL-encoded PlantUML exceeds this limit, the diagram is split to stay within PlantUML server URL length limits. |
| Response note size | 15,000 characters (MaxResponseNoteChunkLength) |
Large response bodies are split across multiple diagram segments with "Continued From Previous Diagram" / "Continued On Next Diagram" markers. |
| Estimated diagram height | 12,000 pixels (MaxEstimatedDiagramHeight) |
When the estimated rendered height exceeds this limit (calculated from arrow count × 45px + note lines × 18px), the diagram is split to prevent excessively tall images. |
Additionally:
- Long URLs exceeding 100 characters are wrapped across multiple lines in the diagram.
-
Lines exceeding 800 characters (
MaxLineWidth) are wrapped to prevent rendering issues.
When a split occurs, the new diagram continues with the same participants and auto-numbered steps, maintaining visual continuity.
Getting Started
Common Tasks
Integration Guides
- Integration xUnit3
- Integration xUnit2
- Integration NUnit
- Integration MSTest
- Integration TUnit
- Integration BDDfy xUnit3
- Integration LightBDD xUnit2
- Integration LightBDD xUnit3
- Integration LightBDD TUnit
- Integration ReqNRoll xUnit2
- Integration ReqNRoll xUnit3
- Integration ReqNRoll TUnit
Extensions
- Integration AtlasDataApi Extension
- Integration BigQuery Extension
- Integration Bigtable Extension
- Integration BlobStorage Extension
- Integration ClickHouse Extension
- Integration CloudStorage Extension
- Integration CosmosDB Extension
- Integration Dapper Extension
- Integration DynamoDB Extension
- Integration EF Core Relational Extension
- Integration Elasticsearch Extension
- Integration EventBridge Extension
- Integration EventHubs Extension
- Integration Grpc Extension
- Integration Kafka Extension
- Integration MassTransit Extension
- Integration MongoDB Extension
- Integration MySqlConnector Extension
- Integration Npgsql Extension
- Integration Oracle Extension
- Integration PubSub Extension
- Integration Redis Extension
- Integration S3 Extension
- Integration ServiceBus Extension
- Integration SNS Extension
- Integration Spanner Extension
- Integration SqlClient Extension
- Integration Sqlite Extension
- Integration SQS Extension
- Integration StorageQueues Extension
- Integration OpenTelemetry Extension
- Integration DispatchProxy Extension
- Integration MediatR Extension
- Integration PlantUML IKVM
Configuration
- Tracking Dependencies
- Tracking Custom Dependencies
- HTTP Tracking Setup
- Report Configuration
- Diagram Customisation
- Phase-Aware Tracking
- Content Formatting
- PlantUML Server Configuration
Features
- Generated Reports
- Search Syntax
- Component Diagrams
- PlantUML Browser Rendering
- Inline SVG Rendering
- Internal Flow Tracking
- Tags and Attributes
- Excluding Requests
- Excluded Headers
- Multi-Host Test Architectures
- Event-Driven Architecture Testing
- Service Bus Tracking Patterns
- Background Thread Correlation
- Parallel-Safe Background Correlation
- Event & Message Tracking
- Assertion Tracking
- Step Tracking
- Tabular Attributes
- Large Response and Diagram Handling
- Diagnostics and Debugging
- CI Summary Integration
- CI Artifact Upload
- Merging Parallel Reports
Reference