You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -10,51 +10,37 @@ Trigger.dev Realtime allows you to trigger, subscribe to, and get real-time upda
10
10
11
11
## Authentication
12
12
13
-
All Realtime subscriptions require authentication so you can securely trigger and subscribe to runs. See our [authentication guide](/realtime/auth) for details on:
14
-
15
-
- Creating Public Access Tokens to subscribe to runs
16
-
- Creating Trigger Tokens to trigger tasks from your frontend
17
-
- Scoping tokens to specific runs, tasks, tags, or batches
18
-
- Auto-generated tokens from `tasks.trigger()`
13
+
All Realtime subscriptions require authentication so you can securely trigger and subscribe to runs. See our [authentication guide](/realtime/auth) for more details.
19
14
20
15
## How run subscriptions work
21
16
22
-
You can subscribe to real-time updates for:
23
-
24
-
-**Specific runs** - Monitor individual run progress
25
-
-**Runs with specific tags** - Track runs by category or user
26
-
-**Task runs** - All runs for specific tasks
27
-
-**Batch runs** - All runs in a batch
28
-
29
-
When you subscribe to runs, you automatically receive the complete [run object](/realtime/run-object) containing status, timestamps, metadata, tags, and more whenever:
17
+
You can subscribe to real-time updates for different scopes of runs:
30
18
31
-
-Run status changes (queued → executing → completed, etc.)
32
-
-[Run metadata](/runs/metadata) is updated
33
-
-[Run tags](/tags) are added or removed
34
-
-[Stream data](/realtime/backend#streams) is emitted
19
+
-**Specific runs** - Monitor individual run progress by run ID
20
+
-**Runs with specific tags** - Track all runs that have certain [tags](/tags) (e.g., all runs tagged with `user:123`)
21
+
-**Batch runs** - All runs within a specific batch
22
+
-**Trigger + subscribe combos** - Trigger a task and immediately subscribe to its run (frontend only)
35
23
36
-
Your tasks can also send additional custom data:
24
+
Once subscribed, you'll receive the complete [run object](/realtime/run-object) with automatic real-time updates whenever the run changes, including:
37
25
38
-
-**Metadata updates** - Update custom metadata on runs that gets streamed to subscribers ([backend](/realtime/backend/metadata) | [React hooks](/realtime/react-hooks/realtime#using-metadata))
39
-
-**Stream function** - Stream data chunks in real-time, perfect for AI/LLM streaming ([backend](/realtime/backend/streams) | [React hooks](/realtime/react-hooks/streams))
26
+
-**Status changes** - queued → executing → completed, etc.
27
+
-**Metadata updates** - Custom progress tracking, status updates, user data, etc. ([backend](/realtime/backend/metadata) | [React hooks](/realtime/react-hooks/realtime#using-metadata))
28
+
-**Tag changes** - When [tags](/tags) are added or removed from the run
29
+
-**Stream data** - Real-time data chunks from your tasks, perfect for AI/LLM streaming ([backend](/realtime/backend/streams) | [React hooks](/realtime/react-hooks/streams))
40
30
41
-
## Implementation approaches
42
-
43
-
### Backend implementation
44
-
45
-
Use our server-side SDK to subscribe to runs from your backend code, other tasks, or serverless functions. Perfect for triggering workflows, sending notifications, or updating databases based on run status changes.
Use our server-side SDK to subscribe to runs from your backend code, other tasks, or serverless functions. Perfect for triggering workflows, sending notifications, or updating databases based on run status changes.
56
42
57
-
Learn more about the underlying technology and run object structure in our [How it Works](/realtime/how-it-works) guide.
0 commit comments