---
search:
  tags:
    - Actions
    - POST
seo:
  description: >-
    Record what the destination confirms happened to an invocation… Reference
    for the POST /api/v2/actions/invocations/{id}/resolve endpoint in the Anlyon
    API.
sidebar:
  label: Resolve an unknown invocation
  badge: POST
title: Resolve an unknown invocation
type: openapi-operation
---
Record what the destination confirms happened to an invocation whose status is `unknown`. Nothing is sent to the destination. Resolved `succeeded` is billed; resolved `failed` releases the reserved usage and refunds the key's budget reservation. The resolution, with its evidence, operator and time, is kept permanently and returned as `resolution`. Only one resolution can win: an invocation that is no longer `unknown` returns `409`. Needs `actions:resolve` (never granted by default) or a workspace admin in the console. The key that requested the invocation can never resolve it. The Idempotency-Key of the original stays taken; to run the action again, invoke with a new key and `retryOf`. An invocation governed by an effect (`effectId` set) is refused with `409` `EFFECT_RESOLUTION_REQUIRED` and the effect in `details.effectId`: resolve the effect at `POST /api/v2/actions/effects/{id}/resolve`, which settles its business allowance too.

`POST /api/v2/actions/invocations/{id}/resolve`