@burdenoff/microfe-bigconsole 2026.1103.7 → 2026.1103.9

package/dist/generated/wspace-operations.d.ts

@@ -920,7 +920,10 @@ export type ContainerSpecInput = {
 };
 /** Content type enum */
 export type ContentType = 'HTML' | 'MARKDOWN' | 'RICH_TEXT' | 'TEXT';
-/** Operation context for filtering and scoping data. All fields are optional and can be extended as needed. */
+/**
+ * Operation context for filtering and scoping data.
+ * All fields are optional and can be extended as needed.
+ */
 export type ContextInput = {
     /** App ID for app-level scoping */
     appId?: string | number | null | undefined;
@@ -1045,6 +1048,7 @@ export type CreateWorkflowInput = {
     description?: string | null | undefined;
     /** ID of an existing workflow in wspace-workflow-svc. When provided, the service skips the bridge call to create a new external workflow and links directly to this ID instead. Used by the FluidGrids SDK onWorkflowSaved callback. */
     externalWorkflowId?: string | null | undefined;
+    /** Unique within the workspace for the lifetime of the workflow, including after deletion. Reusing an active or deleted key returns WORKFLOW_KEY_EXISTS. */
     key: string;
     name: string;
     /** Initial lifecycle status. Defaults to `draft` when omitted, preserving the previous behaviour. The ingest endpoint only accepts payloads for workflows in `active` — a workflow left in `draft` rejects its own delivery with 422. Callers that wire a workflow up completely in one step (definition plus dataSinkKeys) should pass `active` so the chain is usable without a follow-up `updateWorkflow`. Only `draft` and `active` are accepted here. `paused`, `error` and `archived` describe things that can only happen to a workflow that already exists — in particular `error` is written by `executeWorkflow` to mean a real trigger failed — so creating one directly in those states is rejected with `INVALID_INITIAL_WORKFLOW_STATUS`. Use `updateWorkflow` to transition. */