Request
Invoke a function that has been registered with the framework.Response
The framework responds with anInvocationResult message.
string
Message type. Will be
"invocationresult".string
required
UUID that identifies this invocation. Matches the request’s
invocation_id if provided.string
required
The ID of the function that was invoked.
any
The successful result from the function. Omitted if the invocation failed.
object
Error details if the invocation failed. Omitted if successful.
string
W3C trace-context traceparent header, propagated from the request or generated.
string
W3C baggage header, propagated from the request.
Examples
Basic Function Invocation
Request:Invocation with Custom ID
Request:Invocation with Distributed Tracing
Request:Error Cases
Function Not Found
Request:Execution Error
Request:Timeout Error
Error Response:Notes
- The
invocation_idis used to correlate requests with responses - If no
invocation_idis provided, one will be generated automatically - The
resultanderrorfields are mutually exclusive - only one will be present - For HTTP-based functions, the HTTP response body is returned as the
result - For WebSocket-based functions, the worker must send an
InvocationResultmessage - Distributed tracing headers follow the W3C Trace Context specification