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
Copy file name to clipboardExpand all lines: apps/invoke.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ You can invoke your app by making a `POST` request to Kernel's API or via the CL
15
15
16
16
### Asynchronous invocations
17
17
18
-
For long running jobs, use asynchronous invocations to trigger Kernel actions without waiting for the result. You can then poll its[status](/apps/status) for the result.
18
+
For long running jobs, use asynchronous invocations to trigger Kernel actions without waiting for the result. You can then stream real-time[status updates](/apps/status#streaming-status-updates) for the result.
19
19
20
20
<Info>Asynchronous invocations time out after 15 minutes.</Info>
Once you've [deployed](/apps/deploy) an app and invoked it, you can check its status.
8
-
9
-
<GetInvocationStatus />
8
+
Once you've [deployed](/apps/deploy) an app and invoked it, you can monitor its status using streaming for real-time updates or polling for periodic checks.
10
9
11
10
<Info>
12
11
An invocation ends once its code execution finishes.
13
12
</Info>
13
+
14
+
## Streaming Status Updates
15
+
16
+
For real-time status monitoring, use `follow` to [stream invocation events](/api-reference/invocations/stream-invocation-events-via-sse). This provides immediate updates as your invocation progresses and is more efficient than polling.
17
+
18
+
<GetInvocationEvents />
19
+
20
+
### Example
21
+
22
+
Here's an example showing how to handle streaming status updates:
0 commit comments