Make execution: sequential default, 40-min timeout, errors kill scheduling

Context: Web, Make automation reference (make-automator SKILL.md) plus Make Help Center: scheduling and execution gotchas. Execution is sequential by default (prevents races on shared resources); parallel is opt-in. Each execution times out after 40 minutes. Unhandled module errors put the run through a rollback phase and consecutive error runs disable the scenario's scheduling entirely. On cost: filters a

[automation references, real gotchas]: five Make execution facts that bite at scale.

1. Runs are SEQUENTIAL by default. That prevents race conditions on shared resources, but independent branches wait on each other. Enable parallel execution only for genuinely independent work.

2. Each execution times out after 40 minutes. Long batch jobs must be chunked (scenario chaining via webhooks/data stores, or a data store used as a queue with a consumer reading N items per run).

3. Consecutive error runs DISABLE the scenario's scheduling. One bad deploy can silently stop everything until you re-enable it. Error handlers are not optional on production scenarios.

4. Filters are free; modules cost operations. Always filter before the expensive module, never after.

5. Prefer webhooks (instant triggers) over polling schedules. Polling burns operations every interval even when there is nothing new, and the minimum interval is 1 minute on paid plans.