You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: apps/docs/content/docs/en/blocks/function.mdx
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -189,6 +189,8 @@ plt.show()
189
189
190
190
Function blocks receive their code, parameters, resolved references, and previous block context in an internal execution request. Sim can safely reference oversized workflow outputs, such as large `loop.results` or `parallel.results`, when you select a smaller nested field like `<loop.results[0][0].id>`.
191
191
192
+
File outputs are metadata-first by default. Referencing `<file.name>`, `<file.url>`, or similar metadata does not hydrate file contents. Referencing `<file.base64>` explicitly hydrates that file's base64 content at resolver time and can fail if the file exceeds the configured inline limit.
193
+
192
194
Avoid passing a full large object into a Function block when you only need one field. For example, prefer `<api.data.customerId>` over `<api.data>` when the API response is large. If the complete function request body is still larger than the platform limit, execution can fail before your code starts.
193
195
194
196
For large generated data, write the result to a file or table with `outputPath`, `outputSandboxPath`, or `outputTable` instead of returning the entire payload inline.
For large result sets, reference only the entry or field you need, such as `<processtasks.results[10][0].id>`. Sim keeps aggregate results indexable and hydrates stored entries when an indexed path is explicitly referenced.
145
+
146
+
### Batch Size
147
+
148
+
Parallel blocks run up to 20 branches at a time by default. Increase the total count or collection size to process more work; Sim will execute the next batch after the current batch finishes. You can lower the batch size to reduce concurrency for rate-limited APIs.
149
+
143
150
### Instance Isolation
144
151
145
152
Each parallel instance runs independently:
@@ -157,7 +164,7 @@ Each parallel instance runs independently:
157
164
While parallel execution is faster, be mindful of:
158
165
- API rate limits when making concurrent requests
159
166
- Memory usage with large datasets
160
-
- Maximum of 20 concurrent instances to prevent resource exhaustion
167
+
- Maximum of 20 concurrent instances per batch to prevent resource exhaustion
161
168
</Callout>
162
169
163
170
## Parallel vs Loop
@@ -186,6 +193,9 @@ Understanding when to use each:
186
193
<li>
187
194
<strong>Collection</strong>: Array or object to distribute (collection-based)
188
195
</li>
196
+
<li>
197
+
<strong>Batch size</strong>: Number of branches to run concurrently, from 1 to 20
Copy file name to clipboardExpand all lines: apps/docs/content/docs/en/execution/api-deployment.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -232,7 +232,7 @@ Workflow execution responses are capped by platform request and response limits.
232
232
}
233
233
```
234
234
235
-
The `version` field is part of the external API contract. Treat the reference as an opaque placeholder for a value that could not be safely embedded in the response. `id`, `key`, and `executionId` are not fetch URLs; use `selectedOutputs` to request a smaller nested field, reduce the data passed between blocks, or return the data from a Response block when your workflow intentionally owns the HTTP response body.
235
+
The `version` field is part of the external API contract. Treat the reference as an opaque placeholder for a value that could not be safely embedded in the response. `id`, `key`, and `executionId` are not fetch URLs; use `selectedOutputs` to request a smaller nested field, reduce the data passed between blocks, or return the data from a Response block when your workflow intentionally owns the HTTP response body. File outputs are metadata-first; request `.base64` only when you need inline file content.
Copy file name to clipboardExpand all lines: apps/sim/app/workspace/[workspaceId]/w/[workflowId]/components/panel/components/editor/components/subflow-editor/subflow-editor.tsx
Copy file name to clipboardExpand all lines: apps/sim/app/workspace/[workspaceId]/w/[workflowId]/components/panel/components/editor/hooks/use-subflow-editor.ts
0 commit comments