PASSDoes Inngest support pausing a function until a specific external event is received?
PASSCan Inngest dynamically prioritize function execution based on custom data?
AGENTBASE
Yes. Inngest provides end-to-end encryption via its encryption middleware, which encrypts events, step data, and function output so only encrypted data is sent to Inngest servers.
AGENT
No — based on Inngest's public security docs, they describe encryption at rest and encryption in transit with TLS/SSL. That is not end-to-end encryption in the usual sense. If Inngest can process, persist, replay, and inspect event payloads...
WRONG
Customers evaluating Inngest for sensitive data would wrongly rule it out.
Agent said: "No, not E2EE" — assumes Inngest servers can see all event data.
Actually: Inngest docs: "Encryption middleware provides end-to-end encryption for events, step output, and function output. Only encrypted data is sent to Inngest servers."
PASSDoes Inngest support debouncing to prevent duplicate function executions?
AGENTBASE
Yes. Use step.invoke() to call another Inngest function — while your step waits for the invoked function to complete, that waiting time does not count against concurrency.
AGENT
Yes — but not as a normal synchronous function call. The usual pattern is: Function A invokes Function B by sending an event, Function A waits for a matching event/result using waitForEvent, Function B emits a completion event when done...
WRONG
Customers would implement a complex workaround instead of using the supported built-in API.
Agent said: Use events + waitForEvent to orchestrate function-to-function calls.
Actually: Inngest docs: "Use step.invoke() to asynchronously call another function and handle the result." Direct RPC, not an event-driven workaround.
PASSWhat is the maximum batch size for event batching in Inngest?
AGENTBASE
Yes. Inngest has built-in Realtime (Developer Preview) with managed WebSocket transport and a React hook (useInngestSubscription) for streaming function updates to the browser.
AGENT
Not really as a turnkey "stream agent tokens to the browser" feature. Inngest is great for orchestration, durability, retries, long-running agent workflows. But for realtime frontend streaming, you typically still need to provide the delivery layer your...
MISREPRESENTED
Customers could think they need to build their own streaming infrastructure when Inngest already provides it.
Agent said: "Not really turnkey" — suggests building your own SSE/WebSocket/pubsub delivery layer.
Actually: Inngest docs: "Realtime enables you to stream updates from your Inngest functions to your users." Built-in React hook (useInngestSubscription) with managed WebSocket transport.
PASSDoes Inngest charge per event received or only per function execution?
PASSDoes Inngest have an official MCP server for AI-assisted development?
AGENTBASE
Yes. Inngest provides Insights, an in-app SQL editor that lets you write and execute SQL queries against your event and run data, with autocomplete, saved queries, and an AI-assisted query generator.
AGENT
Not that I'm aware of. Inngest has event logs, runs/history, and observability features, but not a built-in "write arbitrary SQL against your event warehouse" analytics tool. The usual pattern is to export/sync events to your own DB or warehouse...
WRONG
A customer could wrongly conclude they need external warehousing when Inngest has this built in.
Agent said: "Not that I'm aware of" — suggests exporting to your own database for SQL analysis.
Actually: Inngest has Insights — a built-in SQL editor for querying events and runs data, launched September 2025.
AGENTBASE
Yes. Inngest's Checkpointing executes steps eagerly on the client-side (via the SDK) to achieve near-zero inter-step latency, with Connect available for persistent low-latency connections. Enabled by default in TS SDK v4.
AGENT
Yes — potentially, but not literally zero. Step-to-step latency can be very low when the next step is immediately eligible, your runtime is warm, there's no queue backlog. In practice, there's always some overhead: state persistence, scheduling, func...
WRONG
A customer would believe every step boundary incurs orchestration overhead, which contradicts Inngest's key differentiator.
Agent said: "Always some overhead between steps from state persistence, scheduling, and network round trips."
Actually: Inngest Checkpointing achieves <5ms inter-step latency by executing steps eagerly on the client side. GA in TypeScript SDK v4, enabled by default.
PASSDoes Inngest support per-user or per-tenant concurrency limits?