Hey everyone! Inspired by a friend of mine I decided I want to offer you free AI Audits for your business. I’m talking about those time-consuming, repetitive, and error-prone tasks that just eat up your day. The administrative "bullshit" that keeps you from doing the high-leverage work that actually moves the needle. I want to help you fix that. I’m opening up a few slots for a Free AI & Process Audit. Basically, we’ll look at your current situation, and I’ll give you a clear roadmap on how to automate those headaches away. The goal is simple: Eliminate the manual grunt work so you have more time for the important stuff (or just more free time). It’s 100% free and casual. If you’re interested, fill out this short form so I can prepare for our chat: 👉 Grab your free audit here: https://tally.so/r/Y5jPAv Let’s get your time back. ⏳

I'm experiencing a persistent RangeError: Invalid string length when processing large datasets in n8n. The workflow executes successfully and processes all data correctly, but fails during the post-execution phase, causing the execution to be marked as "failed" despite successful completion. Error Details Error Message: There was a problem running hook "workflowExecuteAfter" RangeError: Invalid string length at JSON.stringify (<anonymous>) at Push.relayViaPubSub (/usr/local/lib/node_modules/n8n/src/push/index.ts:221:56) at Push.send (/usr/local/lib/node_modules/n8n/src/push/index.ts:169:9) at ExecutionLifecycleHooks.<anonymous> (/usr/local/lib/node_modules/n8n/src/execution-lifecycle/execution-lifecycle-hooks.ts:149:17) Key Details: Dataset Size: Processing ~1159 items per execution n8n Version: 1.98.2 Setup: Docker deployment with Queue mode + Redis + 2 workers Workflow Status: Actually succeeds ("Worker finished execution successfully"), but marked as failed due to Push error What I've Tried Configuration Attempts: bash# Push Backend Settings N8N_PUSH_BACKEND=none # Tried both none and websocket N8N_DISABLE_LIFECYCLE_HOOKS=true # Attempted to disable hooks N8N_DISABLE_UI=true # On workers only # Execution Data Settings EXECUTIONS_DATA_SAVE_ON_SUCCESS=none # Tried to minimize data storage EXECUTIONS_DATA_SAVE_ON_PROGRESS=false EXECUTIONS_DATA_COMPRESS=true # Memory Settings NODE_OPTIONS=--max-old-space-size=40960 # Main container NODE_OPTIONS=--max-old-space-size=61440 # Workers N8N_PAYLOAD_SIZE_MAX=26843545600 Architecture: Main container: UI + Queue management 2 Worker containers: Processing only with N8N_PUSH_BACKEND=none Redis queue with increased timeouts PostgreSQL database Root Cause Analysis The issue appears to be a JavaScript engine limitation rather than an n8n configuration problem: JSON.stringify() Limit: JavaScript has a maximum string length of ~268MB Large Execution Data: When processing 1159 items, the serialized execution data exceeds this limit

We just partnered with 500+ tools and platforms to bring something massive to the community: Annual members of AI Automation Society Plus now get access to $3M+ in SaaS discounts. A few highlights: ✅ 1 year free of Bolt Pro ✅ $1,000 in Airtable credits ✅ $20,000 in waived Stripe fees ✅ 3 months of Perplexity Pro ✅ $25,000 in Azure Cloud credits …plus 532 more. If you’re already on annual, check the new “$3M Savings Vault” course to unlock it. If you’re not yet an annual member and you've been on the fence, this is your sign. The savings alone cover the full cost of the membership. No pressure. Just an insane deal we’re pumped to offer. 🙌 Once again, this offer is for ANNUAL MEMBERS of AIS+ (annual subscription) 👉 Claim up to $3M in savings here