BizTalkArticleGenerationMaxPerRun - System Parameter
New 7.12
BizTalkArticleGenerationMaxPerRun is an integer System Parameter that limits how many Articles one run of Generate Articles from BizTalk may write. The limit applies to every run, whether it starts from the Generate from BizTalk wizard, from an End Point, Integration, System, or Article in the Repository (see Document from the Repository), or from the Web API. A run that would write more Articles is refused. The wizard's Articles step names it next to the run size counter.
The parameter in Administration › Settings › System Parameters, with the default value 50.
At a Glance
| Property | Value |
|---|---|
| Key | BizTalkArticleGenerationMaxPerRun |
| Data type | integer (Articles per run) |
| Default | 50. An update keeps the value you set |
| Read by | Web Client (the wizard's run size counter) and Web API (every generation run) |
| Takes effect | Within about 15 seconds; no restart needed |
| Status | ✅ Active |
| Since | Nodinite 7.12 |
How It Works
- Every Article kind counts against the limit: Integration Articles, Entry Point Articles, and Application Overviews.
- Building Blocks are counted, but not limited.
- The Articles step shows the counter n of max N Articles, broken down per kind, plus at least n Building Blocks. Next is disabled while the counter is over the limit.
- Accept suggestions creates Integration Articles only up to the remaining limit. It always starts from the first Integration Key, so running the wizard again takes the same suggestions. To document the rest, narrow the Integration Key pattern, add Articles with New Integration Article..., or raise this limit.
Choosing a Value
Keep the default for the first runs. Raise it when you regularly hit the limit and your runs finish comfortably; a larger run reads more of the BizTalk management database, writes more documents in one go, and takes longer, most of all when it also generates Nodinite Repository artifacts. To keep the limit and still cover a large BizTalk group, split it over several runs, each with a narrower Integration Key pattern.