GoliathDevelopersGet an API key
Reference/Workflowsgenerated from the gateway manifest

resumeWorkflowVersion

Resume a specific PAUSED version.

POST/api/v1/callWRITEidempotent · 24 hruns as the key's owner
View as Markdown

Resume a specific PAUSED version (by workflowAutomationId), pausing the active sibling first. Promotion is ONE-WAY, so this is NOT a roll-back: it REJECTS a version that is not PAUSED, and it REJECTS a SUPERSEDED version (one with a later-published sibling) with "Only the most recently published version can be resumed." So it can only activate the most recently PUBLISHED paused version. Do not treat resumeWorkflow as an equivalent fallback: it picks the most recently PAUSED version (a different ordering: a version paused later may have been published earlier) and NO-OPS when an active sibling exists, where this op pauses that sibling first. To bring an OLDER version back, use restoreWorkflowVersionAsDraft, never a retry of this op.

curl https://server.goliathdata.com/api/v1/call \
  -H "Authorization: Bearer $GOLIATH_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
    "operationId": "resumeWorkflowVersion",
    "variables": {
      "workflowAutomationId": "<workflowAutomationId>"
    }
  }'
import { GoliathClient } from '@goliath-data/sdk'

const goliath = new GoliathClient({
  apiKey: process.env.GOLIATH_API_KEY!,
  baseUrl: 'https://server.goliathdata.com',
})

const result = await goliath.workflows.resumeWorkflowVersion(
  {
    workflowAutomationId: '<workflowAutomationId>'
  },
  { idempotencyKey: crypto.randomUUID() },
)
const res = await fetch('https://server.goliathdata.com/api/v1/call', {
  method: 'POST',
  headers: {
    Authorization: `Bearer ${process.env.GOLIATH_API_KEY}`,
    'Content-Type': 'application/json',
    'Idempotency-Key': crypto.randomUUID(),
  },
  body: JSON.stringify({
    operationId: 'resumeWorkflowVersion',
    variables: {
      workflowAutomationId: '<workflowAutomationId>'
    }
  }),
})
const { data, errors } = await res.json()

Variables

The example sends only what the schema requires. Some operations also need one of several optional variables (one filter or another, say); the description above says which.

workflowAutomationIdID!required

Response

What comes back under data: a list shows as one entry, and a value as its type.

response shape
{
  "data": {
    "workflowAutomationsMutation": {
      "resumeWorkflowVersion": {
        "id": "<ID>",
        "workflowGroupId": "<ID>",
        "name": "…",
        "status": "DRAFT"
      }
    }
  }
}

Errors

400unknown_variable

A variable the operation does not declare. A typo is refused rather than silently dropped.

401unauthorized

No bearer header, or the key is invalid or revoked.

403insufficient_scope

The key lacks the scope the operation requires.

403forbidden

A referenced record does not exist, was deleted, or is outside your organization. The gateway cannot tell those apart.

409idempotency_conflict

A request with this Idempotency-Key is still in flight.

Idempotency

Send an Idempotency-Key of 1 to 255 characters. A finished request retried with the same key replays its stored response, marked Idempotency-Replayed: true; one still in flight returns 409 idempotency_conflict. Keys expire after 24 hours. Write without fear →

READlistWorkflowsREADgetWorkflowREADgetWorkflowVersionGraphREADlistWorkflowRunsREADgetContentTemplateREADlistContentTemplates