postAutoRunsByIdResumeWithHttpInfo method

Future<Response> postAutoRunsByIdResumeWithHttpInfo(String id)

Release a run waiting at an approval step, with the approval payload

Delivers the durable resume signal to a run parked on a wait_for_approval waitpoint and answers {resumed:true} once the engine has taken it. The body is an ARBITRARY JSON value — object, array, string, number — delivered VERBATIM into the workflow as that waitpoint's output, so it is what the steps after the approval read as their input. An empty body resumes with no payload. That open shape is why this route is not a typed op: an operation's input can carry the payload or the run address, never both. Org-scoped and fails closed: a validated principal is required (403 without one), the run is read under the caller's OWN org so another tenant's run id is a 404, a body that is not JSON is a 400, and a payload over the size limit is a 413 — it becomes durable engine state, so it is bounded here rather than after it lands. The resume is audited as automations.run.resume.

Note: This method returns the HTTP Response.

Parameters:

• String id (required):

Implementation

Future<Response> postAutoRunsByIdResumeWithHttpInfo(String id,) async {
  // ignore: prefer_const_declarations
  final path = r'/v1/auto/runs/{id}/resume'
    .replaceAll('{id}', id);

  // ignore: prefer_final_locals
  Object? postBody;

  final queryParams = <QueryParam>[];
  final headerParams = <String, String>{};
  final formParams = <String, String>{};

  const contentTypes = <String>[];


  return apiClient.invokeAPI(
    path,
    'POST',
    queryParams,
    postBody,
    headerParams,
    formParams,
    contentTypes.isEmpty ? null : contentTypes.first,
  );
}