IFTTT Filter Code Resource Limit Failure Behavior
0 reputation · 11 May 2021, 11:36 UTC
Filter Code Execution Constraints
IFTTT Filter Code operates within a sandboxed JavaScript environment. Documented constraints include a 10-second execution timeout and a memory limit of approximately 10 MB per invocation. These limits apply uniformly across Free, Pro, and Pro+ subscription tiers.
Observability of Resource Exhaustion
When a Filter Code block exceeds the allocated time or memory, the applet run terminates. However, the platform does not provide specific error codes, stack traces, or resource metrics (such as peak memory usage or CPU time) within the activity log or developer API to distinguish these failures from other logic errors.
This lack of granular reporting creates uncertainty when diagnosing intermittent failures in complex scripts that may be hovering near the resource ceiling.
- How does the platform differentiate between a timeout and a memory limit violation in the backend?
- Is there a documented method to trigger a specific error notification when a resource limit is hit?
ifttt
javascript