List a durable function's executions
Changed onReturns the platform's last observed status for each execution; listing does not poll each one. Fetch a single execution for its live state.
Request
- Base URL: https://api.volcano.dev
- URL: https://api.volcano.dev/projects/{id}/durable-functions/{functionId}/executions
- Auth: HTTP bearer
Path parameters
Project ID
Durable function ID, or its name within the project
Query parameters
Page number (1-indexed) for offset pagination. Declares no schema default so the request validator does not inject one: handlers that omit page see it unset (nil) and default to 1 in code, while cursor-first endpoints (e.g. the project deployments feed) can detect its absence to stay in keyset/search mode. Supplying page selects offset pagination.
Number of items per page (max 100)
Lifecycle state of an execution. pending covers the window between the platform reserving the execution name and the function accepting the start, and has no counterpart once the execution is under way. succeeded, failed, timed_out, stopped and unknown are terminal.
unknown means the execution's outcome cannot be established, so no result or error can be given for it. Either it was under way and was never seen to finish, or its start failed with a 500 without the platform establishing whether the execution began — which is why a name whose start returned an error can later read as unknown rather than not being found. It is terminal because nothing can settle it later, and it is rare — treat it as an outcome to retry rather than a state to wait on. A retry under the same name picks this execution back up instead of starting a second one, and needs a free concurrency slot because an unknown execution has given its own up. completed_at on an unknown execution is when the platform gave up, not when the work ended.
Return only executions in this status.
Response
Successful response
Changes
- ○
endpoint added
- ○