@celigo/api-specs 0.2.14 → 0.2.16

package/dist/export.yml

@@ -10298,8 +10298,11 @@ components:
             batchSize:
               type: number
               description: |-
-                Number of records the RESTlet returns per page. Larger pages reduce round-trips but
-                raise NetSuite governance and memory use per call; tune to the record's size.
+                Number of records the RESTlet returns per request (default 1000). This, not the
+                export's `pageSize`, sizes each NetSuite call; the export keeps requesting until the
+                search is exhausted. Larger batches reduce round-trips but raise NetSuite governance
+                and memory use per call; tune to the record's size. In a test run or preview the
+                request is capped at the export's `pageSize` (default 20) instead.
               examples:
                 - 100
                 - 200
@@ -15886,9 +15889,13 @@ components:
             - integer
             - 'null'
           description: |-
-            Number of records per page streamed to downstream flow steps. Pages are additionally
-            capped at 5 MB regardless of record count, so very large records may produce smaller
-            pages. The server does not validate the value.
+            Number of records per page streamed to downstream flow steps when the export is the
+            flow's source step. Pages are additionally capped at 5 MB regardless of record count, so
+            very large records may produce smaller pages. The server does not validate the value.
+            A lookup (`isLookup: true`) runs to completion and hands every result to the incoming
+            record as one response, capped at 5 MB in total, so the value does not change how many
+            results a lookup returns; a result set larger than that belongs in a standalone export
+            step. In a test run or preview the value also caps the records fetched (default 20).
           default: 20
           examples:
             - 100
@@ -15943,7 +15950,11 @@ components:
           description: |-
             When true, the export runs as a mid-flow lookup: it executes once per incoming record,
             using the input record's fields to parameterize the request, and passes the results to
-            subsequent steps. When false, the export runs as a standalone data source.
+            subsequent steps. When false, the export runs as a standalone data source. A lookup's
+            results are not paged through the flow: every page the adaptor fetches is merged into one
+            response for the record, up to 5 MB, so `pageSize` does not limit or extend what a lookup
+            returns. A lookup that must return more than that is better modeled as a standalone
+            export step.
           examples:
             - true
             - false

package/dist/flow.yml

@@ -6737,6 +6737,7 @@ components:
               description: |
                 Total number of errors produced by the job (including resolved ones).
                 Use `numOpenError` for the count of currently unresolved errors.
+                On a parent flow job this is the sum across every step; on a child job it is that step's count.
               examples:
                 - 10
             numOpenError:
@@ -6762,13 +6763,20 @@ components:
             numSuccess:
               type: integer
               readOnly: true
-              description: Number of successful records/pages.
+              description: |-
+                Number of records processed successfully. On a parent flow job (`type: flow`) this is the
+                sum across every step in the run, so one record that passes through an export and an import
+                counts twice. On a child job (`type: export` or `import`) it is that step's count alone.
+                For per-step counts, read the run with `GET /v1/jobs/{_id}/family` or list its children with
+                `GET /v1/jobs?_flowJobId={_id}&type=import`.
               examples:
                 - 10
             numIgnore:
               type: integer
               readOnly: true
-              description: Number of ignored records/pages.
+              description: |-
+                Number of records skipped, for example by an import's ignore-existing or ignore-missing rule.
+                Summed across steps on a parent flow job; per step on a child job.
               examples:
                 - 0
             numExport:

package/dist/import.yml

@@ -1918,7 +1918,9 @@ components:
           description: |-
             Request body template for the import — an array of Handlebars template strings
             positionally aligned with the `method` array (e.g. `["{{{record}}}"]`). A `null`
-            entry means no template for the method at that position.
+            entry means no template for the method at that position. Each entry is a string:
+            write a JSON body as a template string (`["{\"id\": \"{{record.id}}\"}"]`), not as
+            a JSON object, because an object entry does not render as JSON at runtime.
             Leave undefined for standard imports — the Import's mapping step transforms the source record and the mapped data is sent as the request body automatically.
             Set it only when the target API requires XML, SOAP, or a custom structure that mappings cannot produce, or when the user explicitly specifies a request body.
             When set, the mapping step still runs first and the template renders against the post-mapped record — use `{{record.<mappedField>}}` to reference mapping outputs.

package/dist/integration.yml

@@ -1475,13 +1475,15 @@ paths:
         Removes a connection's registration from the integration. This does not delete the connection
         itself -- it only removes it from the integration's registered-connections list.
 
-        Fails while any resource in the integration still uses the connection -- a step
-        (export, import, or lookup) in one of its flows, Tools, or APIs bound to it through
-        `_connectionId`, or an alias on the integration or one of its flows whose
-        `_connectionId` points at it. Move the steps to another connection first (a whole flow
-        at once with `PUT /v1/flows/{_id}/replaceConnection`; Tool and API steps through their
-        own step-level `replaceConnection`), remove any alias that still points at it, then
-        unregister.
+        Fails while any resource in the integration still uses the connection. Two references
+        are known to count: any step in one of its flows, Tools, or APIs whose `_connectionId`
+        is this connection -- every step is an export or import document, whatever its kind
+        (lookup, listener, AI agent, guardrail, Tool wrapper, transfer) -- and an alias on the
+        integration or one of its flows whose `_connectionId` points at it. Move the steps to
+        another connection first (a whole flow at once with
+        `PUT /v1/flows/{_id}/replaceConnection`; Tool and API steps through their own
+        step-level `replaceConnection`), remove or retarget any alias that still points at it,
+        then unregister.
       x-celigo-ai-guidance:
         - |-
           Before calling, list what the integration still binds to this connection: the

package/dist/job.yml

@@ -333,7 +333,9 @@ paths:
         `canceled`, `retried`) are not returned; use `POST /v1/flows/runs/stats` for run history.
 
         The request body contains all filters -- there are no query-string parameters. Narrow to a specific flow or
-        integration with `_flowIds` / `_integrationIds` (AND-combined).
+        integration with `_flowIds` / `_integrationIds` (AND-combined). The time bounds `time_gt` and `time_lte`
+        are accepted but do not narrow this list; to find long-running jobs, compare each job's `createdAt` or
+        `startedAt` on the client.
       requestBody:
         required: true
         content:
@@ -387,6 +389,11 @@ paths:
           The request body supports filtering by integration, flow, status, and
           application.  The platform requires ``sandbox`` in the body; Ora is
           production-only so it always sends ``false``.
+        - |-
+          time_gt and time_lte are accepted but do not narrow this endpoint: a time_lte a week
+          in the past still returns jobs created seconds ago. To find jobs stuck for longer than
+          a threshold, compare each job's createdAt or startedAt yourself, and never describe the
+          result as bounded by a time filter you sent.
   /v1/flows/runs/stats:
     post:
       x-internal: false
@@ -1457,6 +1464,7 @@ components:
               description: |
                 Total number of errors produced by the job (including resolved ones).
                 Use `numOpenError` for the count of currently unresolved errors.
+                On a parent flow job this is the sum across every step; on a child job it is that step's count.
               examples:
                 - 10
             numOpenError:
@@ -1482,13 +1490,20 @@ components:
             numSuccess:
               type: integer
               readOnly: true
-              description: Number of successful records/pages.
+              description: |-
+                Number of records processed successfully. On a parent flow job (`type: flow`) this is the
+                sum across every step in the run, so one record that passes through an export and an import
+                counts twice. On a child job (`type: export` or `import`) it is that step's count alone.
+                For per-step counts, read the run with `GET /v1/jobs/{_id}/family` or list its children with
+                `GET /v1/jobs?_flowJobId={_id}&type=import`.
               examples:
                 - 10
             numIgnore:
               type: integer
               readOnly: true
-              description: Number of ignored records/pages.
+              description: |-
+                Number of records skipped, for example by an import's ignore-existing or ignore-missing rule.
+                Summed across steps on a parent flow job; per step on a child job.
               examples:
                 - 0
             numExport:
@@ -1649,13 +1664,20 @@ components:
         time_gt:
           type: integer
           format: int64
-          description: Optional filter for jobs with `createdAt`/time greater than this epoch milliseconds.
+          description: |-
+            Start of the time window, in epoch milliseconds (exclusive). `POST /v1/flows/runs/stats`
+            aggregates only runs inside the window. `POST /v1/jobs/current` accepts the field but does
+            not apply it: in-progress jobs are returned regardless of when they were created.
           examples:
             - 1745366400000
         time_lte:
           type: integer
           format: int64
-          description: Optional filter for jobs with `createdAt`/time less than or equal to this epoch milliseconds.
+          description: |-
+            End of the time window, in epoch milliseconds (inclusive). `POST /v1/flows/runs/stats`
+            aggregates only runs inside the window. `POST /v1/jobs/current` accepts the field but does
+            not apply it. To find jobs that have been queued or running longer than a threshold, compare
+            each returned job's `createdAt` (queued) or `startedAt` (running) on the client.
           examples:
             - 1746147600000
       required: []

package/dist/template.yml

@@ -507,6 +507,11 @@ paths:
         Installs a template from a previously uploaded zip file. The `runKey`
         in the request body ties this request to the zip upload (obtained from
         `GET /v1/s3SignedURL`).
+
+        The zip carries connection definitions without credentials, and the
+        installed integration receives new connection `_id`s. Configure each
+        connection in the new integration before running its flows; connection
+        `_id`s that existed only in the zip are not preserved.
       requestBody:
         required: true
         content:

package/dist/tool.yml

@@ -10529,7 +10529,9 @@ components:
           description: |-
             Request body template for the import — an array of Handlebars template strings
             positionally aligned with the `method` array (e.g. `["{{{record}}}"]`). A `null`
-            entry means no template for the method at that position.
+            entry means no template for the method at that position. Each entry is a string:
+            write a JSON body as a template string (`["{\"id\": \"{{record.id}}\"}"]`), not as
+            a JSON object, because an object entry does not render as JSON at runtime.
             Leave undefined for standard imports — the Import's mapping step transforms the source record and the mapped data is sent as the request body automatically.
             Set it only when the target API requires XML, SOAP, or a custom structure that mappings cannot produce, or when the user explicitly specifies a request body.
             When set, the mapping step still runs first and the template renders against the post-mapped record — use `{{record.<mappedField>}}` to reference mapping outputs.
@@ -29898,8 +29900,11 @@ components:
             batchSize:
               type: number
               description: |-
-                Number of records the RESTlet returns per page. Larger pages reduce round-trips but
-                raise NetSuite governance and memory use per call; tune to the record's size.
+                Number of records the RESTlet returns per request (default 1000). This, not the
+                export's `pageSize`, sizes each NetSuite call; the export keeps requesting until the
+                search is exhausted. Larger batches reduce round-trips but raise NetSuite governance
+                and memory use per call; tune to the record's size. In a test run or preview the
+                request is capped at the export's `pageSize` (default 20) instead.
               examples:
                 - 100
                 - 200
@@ -32516,9 +32521,13 @@ components:
             - integer
             - 'null'
           description: |-
-            Number of records per page streamed to downstream flow steps. Pages are additionally
-            capped at 5 MB regardless of record count, so very large records may produce smaller
-            pages. The server does not validate the value.
+            Number of records per page streamed to downstream flow steps when the export is the
+            flow's source step. Pages are additionally capped at 5 MB regardless of record count, so
+            very large records may produce smaller pages. The server does not validate the value.
+            A lookup (`isLookup: true`) runs to completion and hands every result to the incoming
+            record as one response, capped at 5 MB in total, so the value does not change how many
+            results a lookup returns; a result set larger than that belongs in a standalone export
+            step. In a test run or preview the value also caps the records fetched (default 20).
           default: 20
           examples:
             - 100
@@ -32573,7 +32582,11 @@ components:
           description: |-
             When true, the export runs as a mid-flow lookup: it executes once per incoming record,
             using the input record's fields to parameterize the request, and passes the results to
-            subsequent steps. When false, the export runs as a standalone data source.
+            subsequent steps. When false, the export runs as a standalone data source. A lookup's
+            results are not paged through the flow: every page the adaptor fetches is merged into one
+            response for the record, up to 5 MB, so `pageSize` does not limit or extend what a lookup
+            returns. A lookup that must return more than that is better modeled as a standalone
+            export step.
           examples:
             - true
             - false

package/package.json

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

package/schemas.json

@@ -1,8 +1,8 @@
 {
 	"provenance": {
 		"repo": "celigo/integrator-api-specs",
-		"iasCommit": "62a17aa",
-		"generatedAt": "2026-09-12"
+		"iasCommit": "aad3947",
+		"generatedAt": "2026-09-13"
 	},
 	"roots": {
 		"aiagent": 121,