docs: document ttl: 0 as opt-out for config-level and task-level TTL

Author: nicktrn

docs/config/config-file.mdx

@@ -364,7 +364,7 @@ export default defineConfig({
 });
 ```
 
-You can override this on a per-task basis by setting `ttl` on the task definition, or per-trigger by passing `ttl` in the trigger options. See [Time-to-live (TTL)](/runs#time-to-live-ttl) for more information.
+You can override this on a per-task basis by setting `ttl` on the task definition, or per-trigger by passing `ttl` in the trigger options. To opt a specific task out of the config-level TTL, set `ttl: 0` on the task. See [Time-to-live (TTL)](/runs#time-to-live-ttl) for more information.
 
 ## Process keep alive
 

docs/runs.mdx

@@ -182,6 +182,29 @@ export default defineConfig({
 });
 ```
 
+To opt out of a config-level or task-level TTL for a specific trigger, pass `ttl: 0`:
+
+```ts
+// This run will not have a TTL, even if the task or config defines one
+await yourTask.trigger({ foo: "bar" }, { ttl: 0 });
+```
+
+Similarly, to opt out of a config-level TTL for a specific task, set `ttl: 0` on the task definition:
+
+```ts
+export const longRunningTask = task({
+  id: "long-running-task",
+  ttl: 0, // Opt out of the config-level TTL
+  run: async (payload) => {
+    //...
+  },
+});
+```
+
+<Note>
+  Setting `ttl: 0` removes the config-level or task-level TTL, but the platform-level maximum still applies. See [Limits - Maximum run TTL](/limits#maximum-run-ttl) for details.
+</Note>
+
 If the run hasn't started within the specified TTL, it will automatically expire, returning the status `Expired`. This is useful for time-sensitive tasks where immediate execution is important. For example, when you queue many runs simultaneously and exceed your concurrency limits, some runs might be delayed - using TTL ensures they only execute if they can start within your specified timeframe.
 
 Dev runs automatically have a 10-minute TTL. On Trigger.dev Cloud, staging and production runs have a maximum TTL of 14 days applied automatically (runs without an explicit TTL get 14 days; longer TTLs are clamped). See [Limits — Maximum run TTL](/limits#maximum-run-ttl) for details.

docs/tasks/overview.mdx

@@ -150,7 +150,7 @@ export const timeSensitiveTask = task({
 });
 ```
 
-You can override this per-trigger by passing `ttl` in the trigger options, or set a project-wide default in your [trigger.config.ts](/config/config-file#ttl). See [Time-to-live (TTL)](/runs#time-to-live-ttl) for more information.
+You can override this per-trigger by passing `ttl` in the trigger options, or set a project-wide default in your [trigger.config.ts](/config/config-file#ttl). Set `ttl: 0` to opt out of a config-level TTL. See [Time-to-live (TTL)](/runs#time-to-live-ttl) for more information.
 
 ## Global lifecycle hooks