Danny/kernel 364 documentation update async invocations section to use #53
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Update the documentation to highlight streaming status updates as the recommended method for retrieving the status of an asynchronous invocation.
Testing
mintlify devworks (see installation here)Visual Proof
TL;DR
Updated the documentation for asynchronous invocations to recommend streaming status updates as the primary method for retrieving invocation status.
Why we made these changes
The previous documentation didn't clearly highlight the benefits of streaming for status updates. This change guides users toward a more efficient, real-time method, reducing the need for polling and improving the developer experience.
What changed?
GET /invocations/{id}/eventsendpoint for streaming status.GET /invocations/{id}) to a secondary alternative.Description generated by Mesa. Update settings