From 357200fbb66e1017267edd089744e4d12b52bb33 Mon Sep 17 00:00:00 2001 From: De Clercq Wentzel <10665586+wentzeld@users.noreply.github.com> Date: Thu, 19 Mar 2026 15:58:51 -0700 Subject: [PATCH 1/3] Add Understanding Workflow Limits documentation page --- src/config/sidebar.ts | 4 + .../operations/understanding-limits.mdx | 179 ++++++++++++++++++ src/content/cre/llms-full-go.txt | 179 ++++++++++++++++++ src/content/cre/llms-full-ts.txt | 179 ++++++++++++++++++ 4 files changed, 541 insertions(+) create mode 100644 src/content/cre/guides/operations/understanding-limits.mdx diff --git a/src/config/sidebar.ts b/src/config/sidebar.ts index 5154c17b055..2768046793e 100644 --- a/src/config/sidebar.ts +++ b/src/config/sidebar.ts @@ -354,6 +354,10 @@ export const SIDEBAR: Partial> = { title: "Simulating Workflows", url: "cre/guides/operations/simulating-workflows", }, + { + title: "Understanding Workflow Limits", + url: "cre/guides/operations/understanding-limits", + }, { title: "Deploying Workflows", url: "cre/guides/operations/deploying-workflows", diff --git a/src/content/cre/guides/operations/understanding-limits.mdx b/src/content/cre/guides/operations/understanding-limits.mdx new file mode 100644 index 00000000000..6760842fcd3 --- /dev/null +++ b/src/content/cre/guides/operations/understanding-limits.mdx @@ -0,0 +1,179 @@ +--- +section: cre +date: Last Modified +title: "Understanding Workflow Limits" +metadata: + description: "Test workflows against production limits locally: use the --limits flag to enforce, disable, or customize simulation limits before deploying." + datePublished: "2026-03-19" + lastModified: "2026-03-19" +--- + +import { Aside, CodeSample } from "@components" + +Simulation limits let you test your workflows against production constraints locally before deploying. By enforcing the same quotas that apply in production, you can catch violations early and avoid surprises at deploy time. + +## Why use simulation limits + +When you simulate a workflow, the CLI can enforce the same [service quotas](/cre/service-quotas) that your workflow will be subject to in production. This helps you: + +- **Catch violations early**: Identify workflows that exceed timeout, memory, or rate limits before deploying. +- **Match production behavior**: Ensure your local simulation mirrors how your workflow will run on the network. +- **Avoid surprises at deploy time**: Confidently deploy knowing your workflow operates within quota boundaries. + +## Using the `--limits` flag + +The `--limits` flag controls how simulation limits are enforced. It supports three modes: + +### Default limits (default behavior) + +By default, the simulator enforces embedded production limits. You do not need to pass any flag: + +```bash +cre workflow simulate my-workflow --target staging-settings +``` + +This is equivalent to explicitly passing `--limits default`: + +```bash +cre workflow simulate my-workflow --limits default --target staging-settings +``` + +### No limits + +To disable all limit enforcement during simulation, use `--limits none`: + +```bash +cre workflow simulate my-workflow --limits none --target staging-settings +``` + + + +### Custom limits + +You can provide a custom limits file to override specific values: + +```bash +cre workflow simulate my-workflow --limits ./my-limits.json --target staging-settings +``` + +See [Customizing limits](#customizing-limits) for how to create a custom limits file. + +## Viewing default limits + +Use the `cre workflow limits export` command to inspect the default production limits: + +```bash +cre workflow limits export +``` + +This outputs a JSON file containing all enforced limits and their default values. You can redirect the output to a file: + +```bash +cre workflow limits export > my-limits.json +``` + +## Customizing limits + +To customize limits for simulation: + +1. **Export the defaults** to a JSON file: + + ```bash + cre workflow limits export > my-limits.json + ``` + +2. **Edit the JSON file** to adjust the values you want to change. For example, you might increase the execution timeout or HTTP call limit for testing purposes. + +3. **Pass the custom file** to the simulator: + + ```bash + cre workflow simulate my-workflow --limits ./my-limits.json --target staging-settings + ``` + + + +## Default limit values + +The exported limits JSON covers the following categories. For the full list of quotas and their values, see the [Service Quotas](/cre/service-quotas) page. + +### Execution limits + +| Limit | Default value | +| ----------------------- | ------------- | +| Execution timeout | 5 minutes | +| Execution response size | 100 KB | +| Execution concurrency | 5 | + +### Capability limits + +| Limit | Default value | +| ----------------------- | ------------- | +| Capability concurrency | 30 | +| Capability call timeout | 3 minutes | +| Secrets concurrency | 5 | + +### Trigger limits + +| Limit | Default value | +| -------------------------- | ------------- | +| Trigger subscription limit | 10 | +| Event queue size | 50 | + +### WASM resource limits + +| Limit | Default value | +| ---------------------- | ------------- | +| Memory | 100 MB | +| Binary size | 100 MB | +| Compressed binary size | 20 MB | +| Config size | 1 MB | +| Secrets size | 1 MB | + +### Trigger-specific limits + +| Limit | Default value | +| --------------------- | ---------------- | +| Cron minimum interval | 30 seconds | +| HTTP trigger rate | 3 per 30 seconds | +| Log event rate | 10 per 6 seconds | + +### Capability-specific limits + +| Limit | Default value | +| ---------------------- | ------------- | +| ChainRead call limit | 15 calls | +| Consensus call limit | 20 calls | +| HTTP call limit | 5 calls | +| ChainWrite targets | 10 targets | +| ChainWrite report size | 5 KB | +| ChainWrite gas limit | 5,000,000 | + +## Requesting limit increases + +If your workflow requires higher limits than the defaults, you can request a limit increase: + +1. Go to [cre.chain.link](https://cre.chain.link) and log in to your account. +2. Click **Help** in the sidebar. +3. Set **Issue Type** to **Other**. +4. In the **Description** field, include: + - Which limit you need increased + - The desired value + - The reason for the increase + + + +## Next steps + +- **Service quotas reference**: See the full [Service Quotas](/cre/service-quotas) page for all quota keys and values. +- **Simulating workflows**: Learn more about the simulation environment in [Simulating Workflows](/cre/guides/operations/simulating-workflows). +- **Deploy your workflow**: Once validated, see [Deploying Workflows](/cre/guides/operations/deploying-workflows). diff --git a/src/content/cre/llms-full-go.txt b/src/content/cre/llms-full-go.txt index 1b80e60a5e7..4d1c8ee1402 100644 --- a/src/content/cre/llms-full-go.txt +++ b/src/content/cre/llms-full-go.txt @@ -386,6 +386,10 @@ These quotas apply to each individual workflow. [Contact us](/cre/support-feedback) to discuss quota increases. + + --- # Support & Feedback @@ -5265,11 +5269,186 @@ Despite these limitations, simulation is an essential tool for catching bugs, va ## Next steps +- **Test against production limits**: Use the `--limits` flag to enforce production quotas during simulation. See [Understanding Workflow Limits](/cre/guides/operations/understanding-limits). - **Deploy your workflow**: Once you're confident your workflow works correctly, see [Deploying Workflows](/cre/guides/operations/deploying-workflows). - **CLI reference**: For a complete list of flags and options, see the [CLI Workflow Commands reference](/cre/reference/cli/workflow/). --- +# Understanding Workflow Limits +Source: https://docs.chain.link/cre/guides/operations/understanding-limits +Last Updated: 2026-03-19 + +Simulation limits let you test your workflows against production constraints locally before deploying. By enforcing the same quotas that apply in production, you can catch violations early and avoid surprises at deploy time. + +## Why use simulation limits + +When you simulate a workflow, the CLI can enforce the same [service quotas](/cre/service-quotas) that your workflow will be subject to in production. This helps you: + +- **Catch violations early**: Identify workflows that exceed timeout, memory, or rate limits before deploying. +- **Match production behavior**: Ensure your local simulation mirrors how your workflow will run on the network. +- **Avoid surprises at deploy time**: Confidently deploy knowing your workflow operates within quota boundaries. + +## Using the `--limits` flag + +The `--limits` flag controls how simulation limits are enforced. It supports three modes: + +### Default limits (default behavior) + +By default, the simulator enforces embedded production limits. You do not need to pass any flag: + +```bash +cre workflow simulate my-workflow --target staging-settings +``` + +This is equivalent to explicitly passing `--limits default`: + +```bash +cre workflow simulate my-workflow --limits default --target staging-settings +``` + +### No limits + +To disable all limit enforcement during simulation, use `--limits none`: + +```bash +cre workflow simulate my-workflow --limits none --target staging-settings +``` + + + +### Custom limits + +You can provide a custom limits file to override specific values: + +```bash +cre workflow simulate my-workflow --limits ./my-limits.json --target staging-settings +``` + +See [Customizing limits](#customizing-limits) for how to create a custom limits file. + +## Viewing default limits + +Use the `cre workflow limits export` command to inspect the default production limits: + +```bash +cre workflow limits export +``` + +This outputs a JSON file containing all enforced limits and their default values. You can redirect the output to a file: + +```bash +cre workflow limits export > my-limits.json +``` + +## Customizing limits + +To customize limits for simulation: + +1. **Export the defaults** to a JSON file: + + ```bash + cre workflow limits export > my-limits.json + ``` + +2. **Edit the JSON file** to adjust the values you want to change. For example, you might increase the execution timeout or HTTP call limit for testing purposes. + +3. **Pass the custom file** to the simulator: + + ```bash + cre workflow simulate my-workflow --limits ./my-limits.json --target staging-settings + ``` + + + +## Default limit values + +The exported limits JSON covers the following categories. For the full list of quotas and their values, see the [Service Quotas](/cre/service-quotas) page. + +### Execution limits + +| Limit | Default value | +| ----------------------- | ------------- | +| Execution timeout | 5 minutes | +| Execution response size | 100 KB | +| Execution concurrency | 5 | + +### Capability limits + +| Limit | Default value | +| ----------------------- | ------------- | +| Capability concurrency | 30 | +| Capability call timeout | 3 minutes | +| Secrets concurrency | 5 | + +### Trigger limits + +| Limit | Default value | +| -------------------------- | ------------- | +| Trigger subscription limit | 10 | +| Event queue size | 50 | + +### WASM resource limits + +| Limit | Default value | +| ---------------------- | ------------- | +| Memory | 100 MB | +| Binary size | 100 MB | +| Compressed binary size | 20 MB | +| Config size | 1 MB | +| Secrets size | 1 MB | + +### Trigger-specific limits + +| Limit | Default value | +| --------------------- | ---------------- | +| Cron minimum interval | 30 seconds | +| HTTP trigger rate | 3 per 30 seconds | +| Log event rate | 10 per 6 seconds | + +### Capability-specific limits + +| Limit | Default value | +| ---------------------- | ------------- | +| ChainRead call limit | 15 calls | +| Consensus call limit | 20 calls | +| HTTP call limit | 5 calls | +| ChainWrite targets | 10 targets | +| ChainWrite report size | 5 KB | +| ChainWrite gas limit | 5,000,000 | + +## Requesting limit increases + +If your workflow requires higher limits than the defaults, you can request a limit increase: + +1. Go to [cre.chain.link](https://cre.chain.link) and log in to your account. +2. Click **Help** in the sidebar. +3. Set **Issue Type** to **Other**. +4. In the **Description** field, include: + - Which limit you need increased + - The desired value + - The reason for the increase + + + +## Next steps + +- **Service quotas reference**: See the full [Service Quotas](/cre/service-quotas) page for all quota keys and values. +- **Simulating workflows**: Learn more about the simulation environment in [Simulating Workflows](/cre/guides/operations/simulating-workflows). +- **Deploy your workflow**: Once validated, see [Deploying Workflows](/cre/guides/operations/deploying-workflows). + +--- + # Deploying Workflows Source: https://docs.chain.link/cre/guides/operations/deploying-workflows Last Updated: 2026-03-17 diff --git a/src/content/cre/llms-full-ts.txt b/src/content/cre/llms-full-ts.txt index 8e194113777..85c5d30e3a6 100644 --- a/src/content/cre/llms-full-ts.txt +++ b/src/content/cre/llms-full-ts.txt @@ -386,6 +386,10 @@ These quotas apply to each individual workflow. [Contact us](/cre/support-feedback) to discuss quota increases. + + --- # Support & Feedback @@ -4380,11 +4384,186 @@ Despite these limitations, simulation is an essential tool for catching bugs, va ## Next steps +- **Test against production limits**: Use the `--limits` flag to enforce production quotas during simulation. See [Understanding Workflow Limits](/cre/guides/operations/understanding-limits). - **Deploy your workflow**: Once you're confident your workflow works correctly, see [Deploying Workflows](/cre/guides/operations/deploying-workflows). - **CLI reference**: For a complete list of flags and options, see the [CLI Workflow Commands reference](/cre/reference/cli/workflow/). --- +# Understanding Workflow Limits +Source: https://docs.chain.link/cre/guides/operations/understanding-limits +Last Updated: 2026-03-19 + +Simulation limits let you test your workflows against production constraints locally before deploying. By enforcing the same quotas that apply in production, you can catch violations early and avoid surprises at deploy time. + +## Why use simulation limits + +When you simulate a workflow, the CLI can enforce the same [service quotas](/cre/service-quotas) that your workflow will be subject to in production. This helps you: + +- **Catch violations early**: Identify workflows that exceed timeout, memory, or rate limits before deploying. +- **Match production behavior**: Ensure your local simulation mirrors how your workflow will run on the network. +- **Avoid surprises at deploy time**: Confidently deploy knowing your workflow operates within quota boundaries. + +## Using the `--limits` flag + +The `--limits` flag controls how simulation limits are enforced. It supports three modes: + +### Default limits (default behavior) + +By default, the simulator enforces embedded production limits. You do not need to pass any flag: + +```bash +cre workflow simulate my-workflow --target staging-settings +``` + +This is equivalent to explicitly passing `--limits default`: + +```bash +cre workflow simulate my-workflow --limits default --target staging-settings +``` + +### No limits + +To disable all limit enforcement during simulation, use `--limits none`: + +```bash +cre workflow simulate my-workflow --limits none --target staging-settings +``` + + + +### Custom limits + +You can provide a custom limits file to override specific values: + +```bash +cre workflow simulate my-workflow --limits ./my-limits.json --target staging-settings +``` + +See [Customizing limits](#customizing-limits) for how to create a custom limits file. + +## Viewing default limits + +Use the `cre workflow limits export` command to inspect the default production limits: + +```bash +cre workflow limits export +``` + +This outputs a JSON file containing all enforced limits and their default values. You can redirect the output to a file: + +```bash +cre workflow limits export > my-limits.json +``` + +## Customizing limits + +To customize limits for simulation: + +1. **Export the defaults** to a JSON file: + + ```bash + cre workflow limits export > my-limits.json + ``` + +2. **Edit the JSON file** to adjust the values you want to change. For example, you might increase the execution timeout or HTTP call limit for testing purposes. + +3. **Pass the custom file** to the simulator: + + ```bash + cre workflow simulate my-workflow --limits ./my-limits.json --target staging-settings + ``` + + + +## Default limit values + +The exported limits JSON covers the following categories. For the full list of quotas and their values, see the [Service Quotas](/cre/service-quotas) page. + +### Execution limits + +| Limit | Default value | +| ----------------------- | ------------- | +| Execution timeout | 5 minutes | +| Execution response size | 100 KB | +| Execution concurrency | 5 | + +### Capability limits + +| Limit | Default value | +| ----------------------- | ------------- | +| Capability concurrency | 30 | +| Capability call timeout | 3 minutes | +| Secrets concurrency | 5 | + +### Trigger limits + +| Limit | Default value | +| -------------------------- | ------------- | +| Trigger subscription limit | 10 | +| Event queue size | 50 | + +### WASM resource limits + +| Limit | Default value | +| ---------------------- | ------------- | +| Memory | 100 MB | +| Binary size | 100 MB | +| Compressed binary size | 20 MB | +| Config size | 1 MB | +| Secrets size | 1 MB | + +### Trigger-specific limits + +| Limit | Default value | +| --------------------- | ---------------- | +| Cron minimum interval | 30 seconds | +| HTTP trigger rate | 3 per 30 seconds | +| Log event rate | 10 per 6 seconds | + +### Capability-specific limits + +| Limit | Default value | +| ---------------------- | ------------- | +| ChainRead call limit | 15 calls | +| Consensus call limit | 20 calls | +| HTTP call limit | 5 calls | +| ChainWrite targets | 10 targets | +| ChainWrite report size | 5 KB | +| ChainWrite gas limit | 5,000,000 | + +## Requesting limit increases + +If your workflow requires higher limits than the defaults, you can request a limit increase: + +1. Go to [cre.chain.link](https://cre.chain.link) and log in to your account. +2. Click **Help** in the sidebar. +3. Set **Issue Type** to **Other**. +4. In the **Description** field, include: + - Which limit you need increased + - The desired value + - The reason for the increase + + + +## Next steps + +- **Service quotas reference**: See the full [Service Quotas](/cre/service-quotas) page for all quota keys and values. +- **Simulating workflows**: Learn more about the simulation environment in [Simulating Workflows](/cre/guides/operations/simulating-workflows). +- **Deploy your workflow**: Once validated, see [Deploying Workflows](/cre/guides/operations/deploying-workflows). + +--- + # Deploying Workflows Source: https://docs.chain.link/cre/guides/operations/deploying-workflows Last Updated: 2026-03-17 From 8f9eacbeac6b42604335b83d11b955827c8a8cea Mon Sep 17 00:00:00 2001 From: De Clercq Wentzel <10665586+wentzeld@users.noreply.github.com> Date: Thu, 19 Mar 2026 16:05:40 -0700 Subject: [PATCH 2/3] rename --- src/config/sidebar.ts | 2 +- .../cre/guides/operations/simulating-workflows.mdx | 1 + .../cre/guides/operations/understanding-limits.mdx | 2 +- src/content/cre/llms-full-go.txt | 8 +++++--- src/content/cre/llms-full-ts.txt | 8 +++++--- src/content/cre/service-quotas.mdx | 6 ++++++ 6 files changed, 19 insertions(+), 8 deletions(-) diff --git a/src/config/sidebar.ts b/src/config/sidebar.ts index f69ceebbfa7..03537570f07 100644 --- a/src/config/sidebar.ts +++ b/src/config/sidebar.ts @@ -360,7 +360,7 @@ export const SIDEBAR: Partial> = { url: "cre/guides/operations/simulating-workflows", }, { - title: "Understanding Workflow Limits", + title: "Testing Production Limits", url: "cre/guides/operations/understanding-limits", }, { diff --git a/src/content/cre/guides/operations/simulating-workflows.mdx b/src/content/cre/guides/operations/simulating-workflows.mdx index f3d5101c4e5..e24a47858a9 100644 --- a/src/content/cre/guides/operations/simulating-workflows.mdx +++ b/src/content/cre/guides/operations/simulating-workflows.mdx @@ -338,5 +338,6 @@ Despite these limitations, simulation is an essential tool for catching bugs, va ## Next steps +- **Test against production limits**: Use the `--limits` flag to enforce production quotas during simulation. See [Testing Production Limits](/cre/guides/operations/understanding-limits). - **Deploy your workflow**: Once you're confident your workflow works correctly, see [Deploying Workflows](/cre/guides/operations/deploying-workflows). - **CLI reference**: For a complete list of flags and options, see the [CLI Workflow Commands reference](/cre/reference/cli/workflow/). diff --git a/src/content/cre/guides/operations/understanding-limits.mdx b/src/content/cre/guides/operations/understanding-limits.mdx index 6760842fcd3..16abd008e23 100644 --- a/src/content/cre/guides/operations/understanding-limits.mdx +++ b/src/content/cre/guides/operations/understanding-limits.mdx @@ -1,7 +1,7 @@ --- section: cre date: Last Modified -title: "Understanding Workflow Limits" +title: "Testing Production Limits" metadata: description: "Test workflows against production limits locally: use the --limits flag to enforce, disable, or customize simulation limits before deploying." datePublished: "2026-03-19" diff --git a/src/content/cre/llms-full-go.txt b/src/content/cre/llms-full-go.txt index c7b74311317..e03f0a1cd51 100644 --- a/src/content/cre/llms-full-go.txt +++ b/src/content/cre/llms-full-go.txt @@ -387,7 +387,9 @@ These quotas apply to each individual workflow. [Contact us](/cre/support-feedback) to discuss quota increases. --- @@ -5269,13 +5271,13 @@ Despite these limitations, simulation is an essential tool for catching bugs, va ## Next steps -- **Test against production limits**: Use the `--limits` flag to enforce production quotas during simulation. See [Understanding Workflow Limits](/cre/guides/operations/understanding-limits). +- **Test against production limits**: Use the `--limits` flag to enforce production quotas during simulation. See [Testing Production Limits](/cre/guides/operations/understanding-limits). - **Deploy your workflow**: Once you're confident your workflow works correctly, see [Deploying Workflows](/cre/guides/operations/deploying-workflows). - **CLI reference**: For a complete list of flags and options, see the [CLI Workflow Commands reference](/cre/reference/cli/workflow/). --- -# Understanding Workflow Limits +# Testing Production Limits Source: https://docs.chain.link/cre/guides/operations/understanding-limits Last Updated: 2026-03-19 diff --git a/src/content/cre/llms-full-ts.txt b/src/content/cre/llms-full-ts.txt index ce84f29a0a9..c4f97585ad8 100644 --- a/src/content/cre/llms-full-ts.txt +++ b/src/content/cre/llms-full-ts.txt @@ -387,7 +387,9 @@ These quotas apply to each individual workflow. [Contact us](/cre/support-feedback) to discuss quota increases. --- @@ -4384,13 +4386,13 @@ Despite these limitations, simulation is an essential tool for catching bugs, va ## Next steps -- **Test against production limits**: Use the `--limits` flag to enforce production quotas during simulation. See [Understanding Workflow Limits](/cre/guides/operations/understanding-limits). +- **Test against production limits**: Use the `--limits` flag to enforce production quotas during simulation. See [Testing Production Limits](/cre/guides/operations/understanding-limits). - **Deploy your workflow**: Once you're confident your workflow works correctly, see [Deploying Workflows](/cre/guides/operations/deploying-workflows). - **CLI reference**: For a complete list of flags and options, see the [CLI Workflow Commands reference](/cre/reference/cli/workflow/). --- -# Understanding Workflow Limits +# Testing Production Limits Source: https://docs.chain.link/cre/guides/operations/understanding-limits Last Updated: 2026-03-19 diff --git a/src/content/cre/service-quotas.mdx b/src/content/cre/service-quotas.mdx index 630beb53a6e..efd50b3afae 100644 --- a/src/content/cre/service-quotas.mdx +++ b/src/content/cre/service-quotas.mdx @@ -144,3 +144,9 @@ These quotas apply to each individual workflow. ## Quota increases [Contact us](/cre/support-feedback) to discuss quota increases. + + From d72b56199fad45efbbf164a7b7c27a9d2796b9f9 Mon Sep 17 00:00:00 2001 From: De Clercq Wentzel <10665586+wentzeld@users.noreply.github.com> Date: Thu, 19 Mar 2026 16:08:11 -0700 Subject: [PATCH 3/3] removing defaults --- .../operations/understanding-limits.mdx | 54 +------------------ src/content/cre/llms-full-go.txt | 54 +------------------ src/content/cre/llms-full-ts.txt | 54 +------------------ 3 files changed, 3 insertions(+), 159 deletions(-) diff --git a/src/content/cre/guides/operations/understanding-limits.mdx b/src/content/cre/guides/operations/understanding-limits.mdx index 16abd008e23..28a70fc03df 100644 --- a/src/content/cre/guides/operations/understanding-limits.mdx +++ b/src/content/cre/guides/operations/understanding-limits.mdx @@ -101,59 +101,7 @@ To customize limits for simulation: ## Default limit values -The exported limits JSON covers the following categories. For the full list of quotas and their values, see the [Service Quotas](/cre/service-quotas) page. - -### Execution limits - -| Limit | Default value | -| ----------------------- | ------------- | -| Execution timeout | 5 minutes | -| Execution response size | 100 KB | -| Execution concurrency | 5 | - -### Capability limits - -| Limit | Default value | -| ----------------------- | ------------- | -| Capability concurrency | 30 | -| Capability call timeout | 3 minutes | -| Secrets concurrency | 5 | - -### Trigger limits - -| Limit | Default value | -| -------------------------- | ------------- | -| Trigger subscription limit | 10 | -| Event queue size | 50 | - -### WASM resource limits - -| Limit | Default value | -| ---------------------- | ------------- | -| Memory | 100 MB | -| Binary size | 100 MB | -| Compressed binary size | 20 MB | -| Config size | 1 MB | -| Secrets size | 1 MB | - -### Trigger-specific limits - -| Limit | Default value | -| --------------------- | ---------------- | -| Cron minimum interval | 30 seconds | -| HTTP trigger rate | 3 per 30 seconds | -| Log event rate | 10 per 6 seconds | - -### Capability-specific limits - -| Limit | Default value | -| ---------------------- | ------------- | -| ChainRead call limit | 15 calls | -| Consensus call limit | 20 calls | -| HTTP call limit | 5 calls | -| ChainWrite targets | 10 targets | -| ChainWrite report size | 5 KB | -| ChainWrite gas limit | 5,000,000 | +The default limits enforced during simulation match the production quotas documented on the [Service Quotas](/cre/service-quotas) page. Use `cre workflow limits export` to inspect the exact values applied to your simulations. ## Requesting limit increases diff --git a/src/content/cre/llms-full-go.txt b/src/content/cre/llms-full-go.txt index e03f0a1cd51..e556bb2115c 100644 --- a/src/content/cre/llms-full-go.txt +++ b/src/content/cre/llms-full-go.txt @@ -5372,59 +5372,7 @@ To customize limits for simulation: ## Default limit values -The exported limits JSON covers the following categories. For the full list of quotas and their values, see the [Service Quotas](/cre/service-quotas) page. - -### Execution limits - -| Limit | Default value | -| ----------------------- | ------------- | -| Execution timeout | 5 minutes | -| Execution response size | 100 KB | -| Execution concurrency | 5 | - -### Capability limits - -| Limit | Default value | -| ----------------------- | ------------- | -| Capability concurrency | 30 | -| Capability call timeout | 3 minutes | -| Secrets concurrency | 5 | - -### Trigger limits - -| Limit | Default value | -| -------------------------- | ------------- | -| Trigger subscription limit | 10 | -| Event queue size | 50 | - -### WASM resource limits - -| Limit | Default value | -| ---------------------- | ------------- | -| Memory | 100 MB | -| Binary size | 100 MB | -| Compressed binary size | 20 MB | -| Config size | 1 MB | -| Secrets size | 1 MB | - -### Trigger-specific limits - -| Limit | Default value | -| --------------------- | ---------------- | -| Cron minimum interval | 30 seconds | -| HTTP trigger rate | 3 per 30 seconds | -| Log event rate | 10 per 6 seconds | - -### Capability-specific limits - -| Limit | Default value | -| ---------------------- | ------------- | -| ChainRead call limit | 15 calls | -| Consensus call limit | 20 calls | -| HTTP call limit | 5 calls | -| ChainWrite targets | 10 targets | -| ChainWrite report size | 5 KB | -| ChainWrite gas limit | 5,000,000 | +The default limits enforced during simulation match the production quotas documented on the [Service Quotas](/cre/service-quotas) page. Use `cre workflow limits export` to inspect the exact values applied to your simulations. ## Requesting limit increases diff --git a/src/content/cre/llms-full-ts.txt b/src/content/cre/llms-full-ts.txt index c4f97585ad8..a6e320590d7 100644 --- a/src/content/cre/llms-full-ts.txt +++ b/src/content/cre/llms-full-ts.txt @@ -4487,59 +4487,7 @@ To customize limits for simulation: ## Default limit values -The exported limits JSON covers the following categories. For the full list of quotas and their values, see the [Service Quotas](/cre/service-quotas) page. - -### Execution limits - -| Limit | Default value | -| ----------------------- | ------------- | -| Execution timeout | 5 minutes | -| Execution response size | 100 KB | -| Execution concurrency | 5 | - -### Capability limits - -| Limit | Default value | -| ----------------------- | ------------- | -| Capability concurrency | 30 | -| Capability call timeout | 3 minutes | -| Secrets concurrency | 5 | - -### Trigger limits - -| Limit | Default value | -| -------------------------- | ------------- | -| Trigger subscription limit | 10 | -| Event queue size | 50 | - -### WASM resource limits - -| Limit | Default value | -| ---------------------- | ------------- | -| Memory | 100 MB | -| Binary size | 100 MB | -| Compressed binary size | 20 MB | -| Config size | 1 MB | -| Secrets size | 1 MB | - -### Trigger-specific limits - -| Limit | Default value | -| --------------------- | ---------------- | -| Cron minimum interval | 30 seconds | -| HTTP trigger rate | 3 per 30 seconds | -| Log event rate | 10 per 6 seconds | - -### Capability-specific limits - -| Limit | Default value | -| ---------------------- | ------------- | -| ChainRead call limit | 15 calls | -| Consensus call limit | 20 calls | -| HTTP call limit | 5 calls | -| ChainWrite targets | 10 targets | -| ChainWrite report size | 5 KB | -| ChainWrite gas limit | 5,000,000 | +The default limits enforced during simulation match the production quotas documented on the [Service Quotas](/cre/service-quotas) page. Use `cre workflow limits export` to inspect the exact values applied to your simulations. ## Requesting limit increases