@celigo/api-specs 0.2.114 → 0.2.115

package/dist/export.yml

@@ -16061,11 +16061,25 @@ components:
             Handlebars template that overrides how each record's unique trace key is generated, used
             to track records through the flow and match retries to prior errors (e.g.
             `{{join "_" record.customerId record.orderId}}`). When omitted, the system picks a unique
-            field automatically. If a transform reshapes the data first, omit the `record.` prefix.
-            Trace keys are capped at 256 characters; a longer key is stored truncated from the middle,
-            keeping the beginning and end of the value. Downstream imports use the trace key as their
-            default concurrency lock key (a blank key means no lock); it never de-duplicates — a record
-            emitted twice with the same key is processed twice.
+            field automatically from the record's top level, by exact field name (`GET
+            /v1/flows/{_id}/traceKey` serves the pattern). The rendered value of a template is stamped
+            on each record as `io_custom_trace_key` and travels downstream with it. If a transform
+            reshapes the data first, omit the `record.` prefix. Trace keys are capped at 256 characters;
+            a longer key is stored truncated from the middle, keeping the beginning and end of the
+            value. Downstream imports use the trace key as their default concurrency lock key (a blank
+            key means no lock); it never de-duplicates — a record emitted twice with the same key is
+            processed twice.
+          x-celigo-ai-guidance:
+            - |-
+              The default derivation reads these top-level fields in order and takes the first present
+              (a record carrying `id` and `internalId` is keyed on `id` alone) — `id`, `Id`, `ID`,
+              `internalid`, `Internalid`, `internalId`, `InternalId`, `INTERNALID`, `_id`, `_Id`, `_ID`,
+              `internal_id`, `internal_Id`, `Internal_id`, `Internal_Id`, `INTERNAL_ID`, `identifier`,
+              `IDENTIFIER` — then a `*anything` rule the platform does not document.
+            - |-
+              A record in flight through the flow carries `io_custom_trace_key` when a template is set
+              — that value is the downstream imports' default lock key; without a template the record
+              carries no trace-key field (the key is derived, not stored on the record).
           examples:
             - '{{record.id}}'
             - '{{join "_" record.customerId record.orderId}}'

package/dist/import.yml

@@ -15944,7 +15944,8 @@ components:
             Handlebars template that generates a concurrency lock key for each record: records that
             render the same key are never submitted at the same time, while records with different
             keys are processed in parallel. When omitted, the record's trace key is the lock key (a
-            blank trace key means no lock); a template replaces that default rather than adding to it.
+            blank trace key means no lock; a custom `traceKeyTemplate` upstream arrives on the record
+            as `io_custom_trace_key`); a template replaces that default rather than adding to it.
             The template is rendered from the record as it arrives at the import — before the import's
             own lookups and mapping run — so a key built from one of the import's lookup results
             (`{{lookup.<name>}}`) or from a mapped field renders empty, and an empty key is no lock at

package/dist/tool.yml

@@ -24812,7 +24812,8 @@ components:
             Handlebars template that generates a concurrency lock key for each record: records that
             render the same key are never submitted at the same time, while records with different
             keys are processed in parallel. When omitted, the record's trace key is the lock key (a
-            blank trace key means no lock); a template replaces that default rather than adding to it.
+            blank trace key means no lock; a custom `traceKeyTemplate` upstream arrives on the record
+            as `io_custom_trace_key`); a template replaces that default rather than adding to it.
             The template is rendered from the record as it arrives at the import — before the import's
             own lookups and mapping run — so a key built from one of the import's lookup results
             (`{{lookup.<name>}}`) or from a mapped field renders empty, and an empty key is no lock at
@@ -36956,11 +36957,25 @@ components:
             Handlebars template that overrides how each record's unique trace key is generated, used
             to track records through the flow and match retries to prior errors (e.g.
             `{{join "_" record.customerId record.orderId}}`). When omitted, the system picks a unique
-            field automatically. If a transform reshapes the data first, omit the `record.` prefix.
-            Trace keys are capped at 256 characters; a longer key is stored truncated from the middle,
-            keeping the beginning and end of the value. Downstream imports use the trace key as their
-            default concurrency lock key (a blank key means no lock); it never de-duplicates — a record
-            emitted twice with the same key is processed twice.
+            field automatically from the record's top level, by exact field name (`GET
+            /v1/flows/{_id}/traceKey` serves the pattern). The rendered value of a template is stamped
+            on each record as `io_custom_trace_key` and travels downstream with it. If a transform
+            reshapes the data first, omit the `record.` prefix. Trace keys are capped at 256 characters;
+            a longer key is stored truncated from the middle, keeping the beginning and end of the
+            value. Downstream imports use the trace key as their default concurrency lock key (a blank
+            key means no lock); it never de-duplicates — a record emitted twice with the same key is
+            processed twice.
+          x-celigo-ai-guidance:
+            - |-
+              The default derivation reads these top-level fields in order and takes the first present
+              (a record carrying `id` and `internalId` is keyed on `id` alone) — `id`, `Id`, `ID`,
+              `internalid`, `Internalid`, `internalId`, `InternalId`, `INTERNALID`, `_id`, `_Id`, `_ID`,
+              `internal_id`, `internal_Id`, `Internal_id`, `Internal_Id`, `INTERNAL_ID`, `identifier`,
+              `IDENTIFIER` — then a `*anything` rule the platform does not document.
+            - |-
+              A record in flight through the flow carries `io_custom_trace_key` when a template is set
+              — that value is the downstream imports' default lock key; without a template the record
+              carries no trace-key field (the key is derived, not stored on the record).
           examples:
             - '{{record.id}}'
             - '{{join "_" record.customerId record.orderId}}'

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@celigo/api-specs",
-  "version": "0.2.114",
+  "version": "0.2.115",
   "private": false,
   "description": "Public OpenAPI bundles (dist/) and the celigo-cli lint schema pack (schemas.json).",
   "keywords": [

package/schemas.json

@@ -1,7 +1,7 @@
 {
 	"provenance": {
 		"repo": "celigo/integrator-api-specs",
-		"iasCommit": "433e7903",
+		"iasCommit": "d2a71cdf",
 		"generatedAt": "2026-10-15"
 	},
 	"roots": {