deepseek-ai/deepseek-harness · error · WorkflowError

META_INVALID

META_INVALID

Error message

invalid meta: ${violations.join('; ')}

What it means

Error "invalid meta: ${violations.join('; ')}" thrown in deepseek-ai/deepseek-harness.

Source

Thrown at packages/workflow/workflow-worker-thread/src/meta.ts:79

      ...record.whenToUse !== undefined ? { whenToUse: record.whenToUse as string } : {},
      ...record.phases !== undefined ? { phases } : {},
    },
  }
}

/**
 * Validate a caller-provided meta value against the {@link WorkflowMeta}
 * contract. Throws `META_INVALID` naming every violation (unknown fields,
 * missing/mistyped `name`/`description`, malformed `phases`); the returned
 * meta is a NORMALIZED copy built from the validated fields, so the engine
 * never aliases the caller's object.
 * @param value - the meta data from the start request (plain JSON by the seam contract).
 * @returns the validated, normalized meta block.
 */
export function validateMeta(value: unknown): WorkflowMeta {
  const { meta, violations } = validateMetaShape(value)
  if (meta === undefined) {
    throw new WorkflowError(`invalid meta: ${violations.join('; ')}`, 'META_INVALID')
  }
  return meta
}

View on GitHub (pinned to b150a551b8)

Solutions

1. Fix the meta fields listed in the violations so they satisfy the meta schema (allowed keys, value types, sizes).

When it happens

Trigger: Thrown at packages/workflow/workflow-worker-thread/src/meta.ts:79 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of deepseek-ai/deepseek-harness@b150a551b8 (2026-08-24). Data as JSON: /api/errors/0fdf9dc0070e17bc. Report an issue: GitHub.