@celigo/api-specs 0.2.144 → 0.2.145

package/dist/export.yml

@@ -15728,6 +15728,11 @@ components:
         `transform` and output `filter` still run on top of them, so downstream steps — and a
         lookup's results mapping — see the transformed, filtered records, not the shape stored here.
 
+        In a flow test run of an HTTP export with a saved mock (live probe, 2026-10-21), the export
+        still listed `request` and `response` stages: `request` held the request the export composes,
+        and `response` held the mock under the source's URL, as did the test run's request log, which
+        recorded it as a 200. Read those stages as the substituted mock, not as a live call.
+
         `POST /v1/exports/preview` reads the `mockOutput` in its request body, not the saved one. For
         an export the preview supports (an HTTP export, for example), a body that carries it (as an
         export read back with GET does) returns that snapshot as a lone `parse` stage without calling

package/dist/flow.yml

@@ -2859,16 +2859,20 @@ paths:
       summary: Search jobs within a flow by trace key
       description: |-
         Searches for flow-run jobs that contain records matching a trace key prefix. Returns up to 1000
-        matching job objects — there is no pagination beyond that limit.
+        matching job objects — there is no pagination beyond that limit. A run matches when it carried
+        a matching record at all, whether the record succeeded, failed or was ignored there (live probe,
+        2026-10-21). Very short prefixes can match nothing — in that probe a two-character prefix of a
+        nine-character key found no run while three characters did — so send the record's whole trace
+        key.
 
-        The `traceKeyPrefix` query parameter is required; the server returns `400` when it is missing.
+        The `traceKeyPrefix` query parameter is required; the server returns `400` ("traceKeyPrefix is
+        required.") when it is missing.
 
-        Known behavior: the `status` filter is accepted but silently ignored — the response always includes
-        jobs of all statuses regardless of the filter value.
+        `status` filters the runs: in the same probe `status=failed` left out a `completed` run that
+        `status=completed` returned, and a value that is not a job status was ignored.
 
         Narrow the window with `createdAt_gte` / `createdAt_lte` when there are many runs for the
-        flow. Because `status` is silently ignored, filter client-side if you need only completed or
-        errored jobs.
+        flow.
       parameters:
         - name: _id
           in: path
@@ -2881,15 +2885,19 @@ paths:
         - name: traceKeyPrefix
           in: query
           required: true
-          description: Trace key prefix to search for. The server matches job records whose `traceKey` begins with this value.
+          description: |-
+            Trace key prefix to search for. The server matches job records whose `traceKey` begins with
+            this value, but very short prefixes can match nothing: in a live probe (2026-10-21) a
+            two-character prefix of a nine-character key found no run while three characters did. Send
+            the record's whole trace key.
           schema:
             type: string
         - name: status
           in: query
           required: false
           description: |-
-            Job status filter. **Note:** this parameter is currently accepted but silently ignored — all
-            statuses are always returned.
+            Job status filter: only runs with this status are returned. A value that is not a job
+            status is ignored (live probe, 2026-10-21).
           schema:
             type: string
         - name: createdAt_gte
@@ -2951,7 +2959,7 @@ paths:
                   value:
                     errors:
                       - code: invalid_request
-                        message: traceKeyPrefix query parameter is required.
+                        message: traceKeyPrefix is required.
         '401':
           $ref: '#/components/responses/401-unauthorized'
         '404':
@@ -3007,7 +3015,7 @@ paths:
             x-enumDescriptions:
               success: The record was processed successfully at this step.
               error: The record encountered an error during processing.
-              ignore: The record was skipped by a filter or routing rule.
+              ignore: The record was skipped at this step, by a filter, a router branch, or an import's ignore-existing or ignore-missing rule.
         - name: _expOrImpId
           in: query
           required: false
@@ -7842,11 +7850,11 @@ components:
           enum:
             - success
             - error
-            - ignored
+            - ignore
           x-enumDescriptions:
             success: The record was processed successfully at this step.
             error: The record encountered an error during processing.
-            ignored: The record was skipped by a filter or routing rule.
+            ignore: The record was skipped at this step, by a filter, a router branch, or an import's ignore-existing or ignore-missing rule.
         timeTaken:
           type: integer
           description: Milliseconds spent processing this record at this step.
@@ -8114,7 +8122,7 @@ components:
           x-enumDescriptions:
             success: The record was processed successfully at this step.
             error: The record encountered an error during processing.
-            ignore: The record was skipped by a filter or routing rule.
+            ignore: The record was skipped at this step, by a filter, a router branch, or an import's ignore-existing or ignore-missing rule.
         timeTaken:
           type: integer
           description: Milliseconds spent processing this record at this step.

package/dist/job.yml

@@ -71,10 +71,13 @@ paths:
         forward, take the `createdAt` of the last record, subtract 1 ms, and
         pass it as `createdAt_lte`.
 
-        Active jobs (`queued` or `running`) are pinned to the top of the first
-        page even when they fall outside the date filters; `canceling` jobs are
-        not pinned. Account for this when paging — the first page can contain
-        records older filters would otherwise exclude.
+        In a live probe (2026-10-21) the date filters applied to a `running`
+        flow job too: created outside `createdAt_gte` / `createdAt_lte`, it was
+        left out of every date-filtered list, whether the query was scoped by
+        flow and integration, by integration, or not at all. `queued` and
+        `canceling` jobs were not tested; if `queued` jobs are pinned to the
+        first page, that page can hold rows the date filters would otherwise
+        exclude, so tolerate out-of-range rows when paging.
       parameters:
         - name: _integrationId
           in: query

package/dist/tool.yml

@@ -36798,6 +36798,11 @@ components:
         `transform` and output `filter` still run on top of them, so downstream steps — and a
         lookup's results mapping — see the transformed, filtered records, not the shape stored here.
 
+        In a flow test run of an HTTP export with a saved mock (live probe, 2026-10-21), the export
+        still listed `request` and `response` stages: `request` held the request the export composes,
+        and `response` held the mock under the source's URL, as did the test run's request log, which
+        recorded it as a 200. Read those stages as the substituted mock, not as a live call.
+
         `POST /v1/exports/preview` reads the `mockOutput` in its request body, not the saved one. For
         an export the preview supports (an HTTP export, for example), a body that carries it (as an
         export read back with GET does) returns that snapshot as a lone `parse` stage without calling

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@celigo/api-specs",
-  "version": "0.2.144",
+  "version": "0.2.145",
   "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": "3543542b",
+		"iasCommit": "325c42fa",
 		"generatedAt": "2026-10-21"
 	},
 	"roots": {