No error handler or failure notification path — Operators cannot tell from external signals that a run failed. Silent failures go undetected until a downstream system shows missing data or a user reports a problem.
Loop calls batch-capable service one item at a time — N items produce N API calls instead of one. This increases latency, accumulates API call cost, and uses more of the provider's rate limit budget.
| Check | Description | Status |
|---|---|---|
| Failure Alerting | Failures silent — only visible in execution log | Missing |
| Retry on Failure | Transient failures cause permanent stops | N/A |
| Request Timeouts | Slow providers can block execution indefinitely | N/A |
| Duplicate Prevention | Retry on write events creates duplicate records | N/A |
| Empty Response Handling | Zero-result lookups break downstream logic | Present |
| AI Output Limits | Output cost and parsing risk unbounded | N/A |
| AI Output Format | Free-form output will break downstream parsers | N/A |
| Activity Logging | Side effects unlogged | N/A |
| Write Deduplication | Webhook replays may create duplicate records | N/A |
Run this analysis on your own workflows
- Build: Article Rows
- Prepare: Split PDFs
- Build: Flag Summary
Operators cannot tell from external signals that a run failed. Silent failures go undetected until a downstream system shows missing data or a user reports a problem.
Connect a dedicated Error Workflow in workflow settings, or add a per-node onError: "continueErrorOutput" path that sends an alert via Slack, email, or a logging service.
- Loop Over Items
- Append: PO Rows to Sheet
N items produce N API calls instead of one. This increases latency, accumulates API call cost, and uses more of the provider's rate limit budget.
Check the service's API for batch or bulk endpoints. Aggregate items before the loop using a Merge or Aggregate node and call the batch endpoint once with all items.
- Form: Completion
These expressions work reliably against test data where all fields are present. In production, fields may be absent, null, or differently typed — causing a runtime error or silent null propagation at the point of the expression.
- In `completionMessage`, change {{ $json.summaryText }} to {{ $json?.summaryText }}.
Currently covers AI/LLM nodes. Non-AI API costs will be added in a future update.
- Loop Over Items
batch API available
Check the service's API for batch or bulk endpoints. Aggregate items before the loop using a Merge or Aggregate node and call the batch endpoint once with all items.
| # | Issue title | Issue description | Affected nodes | |||
|---|---|---|---|---|---|---|
| 1 | Cost Risk | Loop calls batch-capable service one item at a time | Loop node "Loop Over Items" calls "Append: PO Rows to Sheet" with | Loop Over Items, Append: PO Rows to Sheet | Medium | 70% |
| 2 | Reliability | No error handler or failure notification path | Workflow has 3 high-risk nodes (external calls or writes) with no configured error workflow and no inline notification path. If a production execution fails, the failure only appears in execution history. | Build: Article Rows, Prepare: Split PDFs, Build: Flag Summary | Medium | 85% |
| 3 | Reliability | Fragile expression — likely to fail when production data shape differs from test data | Node "Form: Completion" contains expression(s) with risky patterns that assume fields are always present. | Form: Completion | Low | 75% |