Skip to content

Commit

Permalink
Update service-invocation-protocol.md
Browse files Browse the repository at this point in the history 
Co-authored-by: Till Rohrmann <[email protected]>
  • Loading branch information
@slinkydeveloper @tillrohrmann
slinkydeveloper and tillrohrmann authored Dec 21, 2023
1 parent eb450f2 commit 0529da1
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion service-invocation-protocol.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -329,7 +329,7 @@ To notify a failure, the SDK can either:

- Close the stream with `ErrorMessage` as last message. This message is used by the runtime for accurate reporting to
the user.
- Close the stream without `OutputStreamEntry` or `SuspensionMessage` or `ErrorMessage`. This is equivalent to sending
- Close the stream without `EndMessage` or `SuspensionMessage` or `ErrorMessage`. This is equivalent to sending
an `ErrorMessage` with unknown reason.

The runtime takes care of retrying to execute the invocation after such failures occur, following a defined set of
Expand Down

0 comments on commit 0529da1

Please sign in to comment.