@celigo/api-specs 0.2.175 → 0.2.177

package/dist/api.yml

@@ -5460,7 +5460,8 @@ components:
                 - To change throughput while this is true, write `targetConcurrencyLevel`; a `concurrencyLevel` sent in a PUT returns 200 and changes nothing.
                 - Turning it on copies `concurrencyLevel` into `targetConcurrencyLevel`; turning it off unsets the target and leaves `concurrencyLevel` at its current value, which may be below the old target if a recovery was in progress. A `targetConcurrencyLevel` written while this is false is unset by the save.
                 - These four settings (`concurrencyLevel`, `targetConcurrencyLevel`, `_borrowConcurrencyFromConnectionId`, this flag) accept a credential-free `PATCH /v1/connections/{_id}`. A PUT replaces the whole document, so send each secret back as its masked `******` value (that keeps it) or as a new value, and never drop one to keep it — an omitted password or `http.encrypted` is cleared, and a static token left out (with no `refreshMethod`) fails the PUT with 422.
-                - On an `ftp` connection recovery never runs, and transfer threads are `ftp.multiThreadCount`; while this is true a create sets `ftp.concurrencyLevel` to `ftp.targetConcurrencyLevel`, or to 1 without one.
+                - On a create, while this is true, set the level with `targetConcurrencyLevel`: on `http`, `ftp`, `rdbms` and `mongodb` connections the save stores the target sent, or the adaptor's default without one (1 for `ftp`, 5 for `rdbms` and `mongodb`, 25 for `http` where the license's `concurrency` is at least 25), as both fields, whatever `concurrencyLevel` the body carried. A create that sends this as `false` keeps its `concurrencyLevel`.
+                - On an `ftp` connection recovery never runs, and transfer threads are `ftp.multiThreadCount`.
             enableMicroBatchForOneToMany:
               type: boolean
               default: true
@@ -6827,7 +6828,7 @@ components:
             Send no more than the account's licensed maximum (25 standard, 50 with an Environments license).
             A decimal is rejected with 422 `invalid_field_value` on every write (the same rule applies to every
             adaptor's `concurrencyLevel` and `targetConcurrencyLevel`, and to `ftp.multiThreadCount`).
-            Platform-managed while `autoRecoverRateLimitErrors` is true — a PUT ignores the value and the recovery machinery moves it toward the target; set `targetConcurrencyLevel` instead.
+            Platform-managed while `autoRecoverRateLimitErrors` is true — a create or PUT ignores the value (a create without `targetConcurrencyLevel` stores 25 where the license's `concurrency` is at least 25) and the recovery machinery moves it toward the target; set `targetConcurrencyLevel` instead.
             At level 1 an import's pages run one at a time, so a record's existence lookup and write finish before the next record's start (measured on a single import); the import's `idLockTemplate` serializes only same-key records and leaves the rest parallel.
           minimum: 1
           maximum: 50

package/dist/connection.yml

@@ -721,6 +721,12 @@ paths:
           in clear on create and come back masked as "******"; the response also carries the
           server-populated fields (`connectionRole: standard`, `concurrencyLevel`,
           `targetConcurrencyLevel`, `microServices`).
+        - |-
+          Choose the level with `targetConcurrencyLevel`, or send `autoRecoverRateLimitErrors: false`
+          with `concurrencyLevel`. While auto-recovery is on, which a create gets unless it sends
+          `false`, an `http`, `ftp`, `rdbms` or `mongodb` create replaces a `concurrencyLevel` sent
+          without a target with the adaptor's default, so an `http` create that asks for 10 is stored at
+          25 where the license's `concurrency` is at least 25 (see `autoRecoverRateLimitErrors`).
   /v1/connections/{_id}:
     get:
       x-internal: false
@@ -4311,7 +4317,8 @@ components:
                 - To change throughput while this is true, write `targetConcurrencyLevel`; a `concurrencyLevel` sent in a PUT returns 200 and changes nothing.
                 - Turning it on copies `concurrencyLevel` into `targetConcurrencyLevel`; turning it off unsets the target and leaves `concurrencyLevel` at its current value, which may be below the old target if a recovery was in progress. A `targetConcurrencyLevel` written while this is false is unset by the save.
                 - These four settings (`concurrencyLevel`, `targetConcurrencyLevel`, `_borrowConcurrencyFromConnectionId`, this flag) accept a credential-free `PATCH /v1/connections/{_id}`. A PUT replaces the whole document, so send each secret back as its masked `******` value (that keeps it) or as a new value, and never drop one to keep it — an omitted password or `http.encrypted` is cleared, and a static token left out (with no `refreshMethod`) fails the PUT with 422.
-                - On an `ftp` connection recovery never runs, and transfer threads are `ftp.multiThreadCount`; while this is true a create sets `ftp.concurrencyLevel` to `ftp.targetConcurrencyLevel`, or to 1 without one.
+                - On a create, while this is true, set the level with `targetConcurrencyLevel`: on `http`, `ftp`, `rdbms` and `mongodb` connections the save stores the target sent, or the adaptor's default without one (1 for `ftp`, 5 for `rdbms` and `mongodb`, 25 for `http` where the license's `concurrency` is at least 25), as both fields, whatever `concurrencyLevel` the body carried. A create that sends this as `false` keeps its `concurrencyLevel`.
+                - On an `ftp` connection recovery never runs, and transfer threads are `ftp.multiThreadCount`.
             enableMicroBatchForOneToMany:
               type: boolean
               default: true
@@ -5678,7 +5685,7 @@ components:
             Send no more than the account's licensed maximum (25 standard, 50 with an Environments license).
             A decimal is rejected with 422 `invalid_field_value` on every write (the same rule applies to every
             adaptor's `concurrencyLevel` and `targetConcurrencyLevel`, and to `ftp.multiThreadCount`).
-            Platform-managed while `autoRecoverRateLimitErrors` is true — a PUT ignores the value and the recovery machinery moves it toward the target; set `targetConcurrencyLevel` instead.
+            Platform-managed while `autoRecoverRateLimitErrors` is true — a create or PUT ignores the value (a create without `targetConcurrencyLevel` stores 25 where the license's `concurrency` is at least 25) and the recovery machinery moves it toward the target; set `targetConcurrencyLevel` instead.
             At level 1 an import's pages run one at a time, so a record's existence lookup and write finish before the next record's start (measured on a single import); the import's `idLockTemplate` serializes only same-key records and leaves the rest parallel.
           minimum: 1
           maximum: 50
@@ -9663,6 +9670,13 @@ components:
             drops to 1 and climbs back toward the adaptor block's `targetConcurrencyLevel`, which is the
             throughput lever while this is on. Turning it on copies the current `concurrencyLevel` into
             the target; turning it off unsets the target and leaves `concurrencyLevel` at its current value.
+            A create gets `true` unless it sends `false`; while it is true, set a new connection's level
+            with `targetConcurrencyLevel`. On `http`, `ftp`, `rdbms` and `mongodb` connections the create
+            stores the target sent, or the adaptor's default without one, as both `concurrencyLevel` and
+            `targetConcurrencyLevel`, whatever `concurrencyLevel` the body carried: 1 for `ftp`, 5 for
+            `rdbms` and `mongodb`, and 25 for `http` where the license's `concurrency` is at least 25, so
+            such an `http` create that sends only `concurrencyLevel: 10` is stored at 25. To keep the
+            `concurrencyLevel` you send, create with this `false`.
             Recovery never runs on `ftp` connections: FTP errors aren't treated as rate limits.
         __integrationIds:
           type: array

package/dist/enduser.yml

@@ -2368,7 +2368,8 @@ components:
                 - To change throughput while this is true, write `targetConcurrencyLevel`; a `concurrencyLevel` sent in a PUT returns 200 and changes nothing.
                 - Turning it on copies `concurrencyLevel` into `targetConcurrencyLevel`; turning it off unsets the target and leaves `concurrencyLevel` at its current value, which may be below the old target if a recovery was in progress. A `targetConcurrencyLevel` written while this is false is unset by the save.
                 - These four settings (`concurrencyLevel`, `targetConcurrencyLevel`, `_borrowConcurrencyFromConnectionId`, this flag) accept a credential-free `PATCH /v1/connections/{_id}`. A PUT replaces the whole document, so send each secret back as its masked `******` value (that keeps it) or as a new value, and never drop one to keep it — an omitted password or `http.encrypted` is cleared, and a static token left out (with no `refreshMethod`) fails the PUT with 422.
-                - On an `ftp` connection recovery never runs, and transfer threads are `ftp.multiThreadCount`; while this is true a create sets `ftp.concurrencyLevel` to `ftp.targetConcurrencyLevel`, or to 1 without one.
+                - On a create, while this is true, set the level with `targetConcurrencyLevel`: on `http`, `ftp`, `rdbms` and `mongodb` connections the save stores the target sent, or the adaptor's default without one (1 for `ftp`, 5 for `rdbms` and `mongodb`, 25 for `http` where the license's `concurrency` is at least 25), as both fields, whatever `concurrencyLevel` the body carried. A create that sends this as `false` keeps its `concurrencyLevel`.
+                - On an `ftp` connection recovery never runs, and transfer threads are `ftp.multiThreadCount`.
             enableMicroBatchForOneToMany:
               type: boolean
               default: true
@@ -3735,7 +3736,7 @@ components:
             Send no more than the account's licensed maximum (25 standard, 50 with an Environments license).
             A decimal is rejected with 422 `invalid_field_value` on every write (the same rule applies to every
             adaptor's `concurrencyLevel` and `targetConcurrencyLevel`, and to `ftp.multiThreadCount`).
-            Platform-managed while `autoRecoverRateLimitErrors` is true — a PUT ignores the value and the recovery machinery moves it toward the target; set `targetConcurrencyLevel` instead.
+            Platform-managed while `autoRecoverRateLimitErrors` is true — a create or PUT ignores the value (a create without `targetConcurrencyLevel` stores 25 where the license's `concurrency` is at least 25) and the recovery machinery moves it toward the target; set `targetConcurrencyLevel` instead.
             At level 1 an import's pages run one at a time, so a record's existence lookup and write finish before the next record's start (measured on a single import); the import's `idLockTemplate` serializes only same-key records and leaves the rest parallel.
           minimum: 1
           maximum: 50

package/dist/export.yml

@@ -5608,31 +5608,37 @@ components:
           description: |-
             Selects which files are processed: files matching the filter criteria are exported,
             and non-matching files are skipped entirely before processing begins. Filterable
-            fields come from each file's metadata — most providers expose filename, filesize,
-            and lastmodified (e.g. ["endswith", ["string", ["extract", "filename"]], ".csv"]).
+            fields come from each file's listing entry: the name as `fileName`, the size as
+            `filesize`, and the modified time as `lastModifiedTime` on FTP, SFTP and S3 or
+            `modifiedTime` on cloud-storage folders (`http.type: "file"`)
+            (e.g. ["endswith", ["string", ["extract", "fileName"]], ".csv"]). There is no
+            `lastmodified` key.
           allOf:
             - $ref: '#/components/schemas/Filter'
           x-celigo-ai-guidance:
             - |-
               ## AVAILABLE FILTER FIELDS
 
-              The specific fields available for file filtering are the contained in the `fileMeta` property. 
+              The fields a file filter reads are on each file's listing entry, before the file is
+              downloaded. They are not the records' `fileMeta`, though some names match.
 
               ### Common Filter Fields
 
               These are the most commonly available fields across most file providers:
 
-              1. **filename**: The name of the file (with extension)
+              1. **fileName**: The name of the file (with extension)
                 - Example filter: Match files with specific extensions or naming patterns
-                - Usage: `["endswith", ["string", ["extract", "filename"]], ".csv"]`
+                - Usage: `["endswith", ["string", ["extract", "fileName"]], ".csv"]`
 
               2. **filesize**: The size of the file in bytes
                 - Example filter: Skip files that are too large or too small
                 - Usage: `["lessthan", ["number", ["extract", "filesize"]], 1000000]`
 
-              3. **lastmodified**: The last modification timestamp of the file
+              3. **lastModifiedTime** (FTP, SFTP, S3) or **modifiedTime** (cloud-storage folders): The
+                 last modification timestamp of the file. There is no `lastmodified` key.
                 - Example filter: Process only files created/modified within a specific date range
-                - Usage: `["greaterthan", ["epochtime", ["extract", "lastmodified"]], 1672531200000]` (2023-01-01T00:00:00Z in epoch milliseconds)
+                - Usage (FTP, SFTP, S3): `["greaterthan", ["epochtime", ["extract", "lastModifiedTime"]], 1672531200000]` (2023-01-01T00:00:00Z in epoch milliseconds)
+                - Usage (cloud-storage folders): `["greaterthan", ["epochtime", ["extract", "modifiedTime"]], 1672531200000]`
         backupPath:
           type: string
           description: Path where backup copies of source files are stored before processing.
@@ -6636,7 +6642,10 @@ components:
             - async_helper
         once:
           type: object
-          description: Callback configuration for once exports, used to mark records as exported in the source system after successful processing.
+          description: |-
+            Callback configuration for once exports, used to mark records as exported in the source system after successful processing.
+            Called only while the export's `type` is `once`: an export with no `type` keeps a saved `once` and never calls it, so every
+            run reads every record again (live-verified 2026-10-22).
           properties:
             relativeURI:
               type: string

package/dist/flow.yml

@@ -7208,7 +7208,10 @@ components:
                 - retry
                 - bulk_retry
               x-enumDescriptions:
-                export: A child job for an export step within a flow run.
+                export: |-
+                  A child job for an export step within a flow run: the flow's source export, or a
+                  lookup step (an export with `isLookup`), whose job counts the pages it looked up in
+                  `numPagesProcessed`.
                 import: A child job for an import step within a flow run.
                 flow: A parent flow-run job that orchestrates the full pipeline.
                 retry: A retry of a single failed record from a previous job.
@@ -7438,8 +7441,9 @@ components:
               type: integer
               readOnly: true
               description: |-
-                Number of records skipped, by a filter or by an import's ignore-existing or ignore-missing
-                rule. Records an import's filter skips count in that import's child job; records an export's
+                Number of records skipped: by a filter, by an import's ignore-existing or ignore-missing
+                rule, by an import's preMap hook that returned no data for the record, or by a lookup step's
+                input filter (the record continues without the lookup's data). Records an import's filter skips count in that import's child job; records an export's
                 output filter drops count in the export's child job, whose `numSuccess` then counts only the
                 records that passed (an export that read 6 records and dropped 3 reads `numSuccess` 3,
                 `numIgnore` 3; live-verified 2026-10-22). Filtered records raise no error.
@@ -7466,7 +7470,10 @@ components:
             numPagesProcessed:
               type: integer
               readOnly: true
-              description: Number of pages processed by downstream imports.
+              description: |-
+                Number of pages processed by downstream steps: imports and lookup steps. A source export's
+                child job reads 0, a lookup step's and an import's count the pages they processed, and a
+                parent flow job sums its children.
               examples:
                 - 10
             oIndex:
@@ -8080,11 +8087,13 @@ 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 step skipped the record: its filter, a preMap hook that returned no data for the
+              record, or an ignore-existing or ignore-missing rule. `stage` names which.
         timeTaken:
           type: integer
           description: Milliseconds spent at this step for this record.
@@ -8106,8 +8115,14 @@ components:
             Pipeline stage at which this step entry was recorded. Observed values include `apiCall`
             (the adaptor invocation itself). Useful for filtering metadata responses when a step has
             multiple stage entries across a single record's pass.
+
+            On an entry with `status: ignore`, the stage that skipped the record, recorded even on a run
+            logged at `basic` (whose stage data is empty): `inputFilter` for the step's filter,
+            `preMapHook` for a preMap hook that returned no data for the record, and an empty string for
+            an ignore-existing rule.
           examples:
             - apiCall
+            - inputFilter
     ExecutionLogMetadataResponse:
       type: object
       description: |-

package/dist/import.yml

@@ -5418,7 +5418,7 @@ components:
               - bulk_load
           x-enumDescriptions:
             INSERT: Legacy value for insert operations; use bulk_insert or per_record instead.
-            UPDATE: Legacy value for update operations; use per_record instead.
+            UPDATE: Legacy value for update operations; use per_page or per_record instead.
             bulk_insert: Batch INSERT via multi-row VALUES clause for efficient bulk data loading.
             per_record: Execute one SQL statement per record, giving full control over individual record SQL.
             per_page: Execute one SQL statement per page (batch) of records.
@@ -5428,7 +5428,7 @@ components:
           description: |-
             Execution strategy for the SQL operation, which determines the required companion field: per_record, per_page, and first_page require `query`; bulk_insert requires `bulkInsert`; bulk_load requires `bulkLoad`.
             Prefer the highest-performance type the operation supports: bulk_load (Snowflake, Google BigQuery, Microsoft SQL Server on a cloud connection, Azure Synapse and Amazon Redshift — handles INSERT, upsert via `bulkLoad.primaryKeys`, and custom merge or ignore-existing logic via `bulkLoad.overrideMergeQuery`), then bulk_insert for pure INSERTs, then per_page, then per_record only when the logic cannot be expressed as a batch operation.
-            For UPDATE, UPSERT, or ignore-existing logic on databases without bulk_load support, use per_page or per_record with `query` — bulk_insert has no duplicate-checking logic.
+            For UPDATE, UPSERT, or ignore-existing logic on databases without bulk_load support, use per_page or per_record with `query` — bulk_insert has no duplicate-checking logic. Prefer per_page when the statement can loop `batch_of_records`, and use per_record when the SQL can't be written as one batch statement.
             Set a single value; do not combine types or use the legacy INSERT and UPDATE values.
             per_page statements render against the whole batch (`batch_of_records`) rather than a single record — loop with `{{#each batch_of_records}}...{{record.fieldName}}...{{/each}}`, with the same quoting as `query` (double braces for strings, triple for numbers).
 
@@ -5490,9 +5490,10 @@ components:
               ### UPDATE Operation
               Prompt: "Update inventory counts"
               ```json
-              "queryType": ["per_record"],
-              "query": ["UPDATE inventory SET qty = {{{record.qty}}} WHERE sku = {{record.sku}}"]
+              "queryType": ["per_page"],
+              "query": ["{{#each batch_of_records}}UPDATE inventory SET qty = {{{record.qty}}} WHERE sku = {{record.sku}};{{/each}}"]
               ```
+              Use `"queryType": ["per_record"]` with `"query": ["UPDATE inventory SET qty = {{{record.qty}}} WHERE sku = {{record.sku}}"]` when the SQL can't be written as one batch statement.
 
               ### Run Once Per Page
               Prompt: "Execute this stored procedure for each page of results"
@@ -5510,7 +5511,7 @@ components:
           type: object
           description: |-
             Configuration for batch INSERTs via a multi-row VALUES clause; required when queryType is `["bulk_insert"]` and must not be set otherwise.
-            Only suited to pure INSERTs — for UPDATE, UPSERT, or ignore-existing/skip-duplicates logic, use queryType `["per_record"]` with the `query` field instead.
+            Only suited to pure INSERTs — for UPDATE or UPSERT, use queryType `["per_page"]` (a statement that loops `batch_of_records`) or `["per_record"]` with the `query` field instead, and for ignore-existing/skip-duplicates logic `["per_record"]`.
           x-celigo-ai-guidance:
             - |-
               **CRITICAL: This object is ONLY used when `queryType` is `["bulk_insert"]`.**
@@ -5520,7 +5521,7 @@ components:
               - Pure INSERT operation with NO ignoreExisting/duplicate checking
 
               ❌ **DO NOT SET THIS** when:
-              - `queryType` is `["per_record"]` (use `query` field instead)
+              - `queryType` is `["per_page"]` or `["per_record"]` (use the `query` field instead)
               - Operation involves UPDATE, UPSERT, or ignoreExisting logic
 
               If the prompt mentions "ignore existing", "skip duplicates", or "match on field",

package/dist/job.yml

@@ -1341,7 +1341,10 @@ components:
                 - retry
                 - bulk_retry
               x-enumDescriptions:
-                export: A child job for an export step within a flow run.
+                export: |-
+                  A child job for an export step within a flow run: the flow's source export, or a
+                  lookup step (an export with `isLookup`), whose job counts the pages it looked up in
+                  `numPagesProcessed`.
                 import: A child job for an import step within a flow run.
                 flow: A parent flow-run job that orchestrates the full pipeline.
                 retry: A retry of a single failed record from a previous job.
@@ -1571,8 +1574,9 @@ components:
               type: integer
               readOnly: true
               description: |-
-                Number of records skipped, by a filter or by an import's ignore-existing or ignore-missing
-                rule. Records an import's filter skips count in that import's child job; records an export's
+                Number of records skipped: by a filter, by an import's ignore-existing or ignore-missing
+                rule, by an import's preMap hook that returned no data for the record, or by a lookup step's
+                input filter (the record continues without the lookup's data). Records an import's filter skips count in that import's child job; records an export's
                 output filter drops count in the export's child job, whose `numSuccess` then counts only the
                 records that passed (an export that read 6 records and dropped 3 reads `numSuccess` 3,
                 `numIgnore` 3; live-verified 2026-10-22). Filtered records raise no error.
@@ -1599,7 +1603,10 @@ components:
             numPagesProcessed:
               type: integer
               readOnly: true
-              description: Number of pages processed by downstream imports.
+              description: |-
+                Number of pages processed by downstream steps: imports and lookup steps. A source export's
+                child job reads 0, a lookup step's and an import's count the pages they processed, and a
+                parent flow job sums its children.
               examples:
                 - 10
             oIndex:

package/dist/mcp-server.yml

@@ -4204,7 +4204,8 @@ components:
                 - To change throughput while this is true, write `targetConcurrencyLevel`; a `concurrencyLevel` sent in a PUT returns 200 and changes nothing.
                 - Turning it on copies `concurrencyLevel` into `targetConcurrencyLevel`; turning it off unsets the target and leaves `concurrencyLevel` at its current value, which may be below the old target if a recovery was in progress. A `targetConcurrencyLevel` written while this is false is unset by the save.
                 - These four settings (`concurrencyLevel`, `targetConcurrencyLevel`, `_borrowConcurrencyFromConnectionId`, this flag) accept a credential-free `PATCH /v1/connections/{_id}`. A PUT replaces the whole document, so send each secret back as its masked `******` value (that keeps it) or as a new value, and never drop one to keep it — an omitted password or `http.encrypted` is cleared, and a static token left out (with no `refreshMethod`) fails the PUT with 422.
-                - On an `ftp` connection recovery never runs, and transfer threads are `ftp.multiThreadCount`; while this is true a create sets `ftp.concurrencyLevel` to `ftp.targetConcurrencyLevel`, or to 1 without one.
+                - On a create, while this is true, set the level with `targetConcurrencyLevel`: on `http`, `ftp`, `rdbms` and `mongodb` connections the save stores the target sent, or the adaptor's default without one (1 for `ftp`, 5 for `rdbms` and `mongodb`, 25 for `http` where the license's `concurrency` is at least 25), as both fields, whatever `concurrencyLevel` the body carried. A create that sends this as `false` keeps its `concurrencyLevel`.
+                - On an `ftp` connection recovery never runs, and transfer threads are `ftp.multiThreadCount`.
             enableMicroBatchForOneToMany:
               type: boolean
               default: true
@@ -5571,7 +5572,7 @@ components:
             Send no more than the account's licensed maximum (25 standard, 50 with an Environments license).
             A decimal is rejected with 422 `invalid_field_value` on every write (the same rule applies to every
             adaptor's `concurrencyLevel` and `targetConcurrencyLevel`, and to `ftp.multiThreadCount`).
-            Platform-managed while `autoRecoverRateLimitErrors` is true — a PUT ignores the value and the recovery machinery moves it toward the target; set `targetConcurrencyLevel` instead.
+            Platform-managed while `autoRecoverRateLimitErrors` is true — a create or PUT ignores the value (a create without `targetConcurrencyLevel` stores 25 where the license's `concurrency` is at least 25) and the recovery machinery moves it toward the target; set `targetConcurrencyLevel` instead.
             At level 1 an import's pages run one at a time, so a record's existence lookup and write finish before the next record's start (measured on a single import); the import's `idLockTemplate` serializes only same-key records and leaves the rest parallel.
           minimum: 1
           maximum: 50

package/dist/tool.yml

@@ -7738,7 +7738,8 @@ components:
                 - To change throughput while this is true, write `targetConcurrencyLevel`; a `concurrencyLevel` sent in a PUT returns 200 and changes nothing.
                 - Turning it on copies `concurrencyLevel` into `targetConcurrencyLevel`; turning it off unsets the target and leaves `concurrencyLevel` at its current value, which may be below the old target if a recovery was in progress. A `targetConcurrencyLevel` written while this is false is unset by the save.
                 - These four settings (`concurrencyLevel`, `targetConcurrencyLevel`, `_borrowConcurrencyFromConnectionId`, this flag) accept a credential-free `PATCH /v1/connections/{_id}`. A PUT replaces the whole document, so send each secret back as its masked `******` value (that keeps it) or as a new value, and never drop one to keep it — an omitted password or `http.encrypted` is cleared, and a static token left out (with no `refreshMethod`) fails the PUT with 422.
-                - On an `ftp` connection recovery never runs, and transfer threads are `ftp.multiThreadCount`; while this is true a create sets `ftp.concurrencyLevel` to `ftp.targetConcurrencyLevel`, or to 1 without one.
+                - On a create, while this is true, set the level with `targetConcurrencyLevel`: on `http`, `ftp`, `rdbms` and `mongodb` connections the save stores the target sent, or the adaptor's default without one (1 for `ftp`, 5 for `rdbms` and `mongodb`, 25 for `http` where the license's `concurrency` is at least 25), as both fields, whatever `concurrencyLevel` the body carried. A create that sends this as `false` keeps its `concurrencyLevel`.
+                - On an `ftp` connection recovery never runs, and transfer threads are `ftp.multiThreadCount`.
             enableMicroBatchForOneToMany:
               type: boolean
               default: true
@@ -9105,7 +9106,7 @@ components:
             Send no more than the account's licensed maximum (25 standard, 50 with an Environments license).
             A decimal is rejected with 422 `invalid_field_value` on every write (the same rule applies to every
             adaptor's `concurrencyLevel` and `targetConcurrencyLevel`, and to `ftp.multiThreadCount`).
-            Platform-managed while `autoRecoverRateLimitErrors` is true — a PUT ignores the value and the recovery machinery moves it toward the target; set `targetConcurrencyLevel` instead.
+            Platform-managed while `autoRecoverRateLimitErrors` is true — a create or PUT ignores the value (a create without `targetConcurrencyLevel` stores 25 where the license's `concurrency` is at least 25) and the recovery machinery moves it toward the target; set `targetConcurrencyLevel` instead.
             At level 1 an import's pages run one at a time, so a record's existence lookup and write finish before the next record's start (measured on a single import); the import's `idLockTemplate` serializes only same-key records and leaves the rest parallel.
           minimum: 1
           maximum: 50
@@ -16995,7 +16996,7 @@ components:
               - bulk_load
           x-enumDescriptions:
             INSERT: Legacy value for insert operations; use bulk_insert or per_record instead.
-            UPDATE: Legacy value for update operations; use per_record instead.
+            UPDATE: Legacy value for update operations; use per_page or per_record instead.
             bulk_insert: Batch INSERT via multi-row VALUES clause for efficient bulk data loading.
             per_record: Execute one SQL statement per record, giving full control over individual record SQL.
             per_page: Execute one SQL statement per page (batch) of records.
@@ -17005,7 +17006,7 @@ components:
           description: |-
             Execution strategy for the SQL operation, which determines the required companion field: per_record, per_page, and first_page require `query`; bulk_insert requires `bulkInsert`; bulk_load requires `bulkLoad`.
             Prefer the highest-performance type the operation supports: bulk_load (Snowflake, Google BigQuery, Microsoft SQL Server on a cloud connection, Azure Synapse and Amazon Redshift — handles INSERT, upsert via `bulkLoad.primaryKeys`, and custom merge or ignore-existing logic via `bulkLoad.overrideMergeQuery`), then bulk_insert for pure INSERTs, then per_page, then per_record only when the logic cannot be expressed as a batch operation.
-            For UPDATE, UPSERT, or ignore-existing logic on databases without bulk_load support, use per_page or per_record with `query` — bulk_insert has no duplicate-checking logic.
+            For UPDATE, UPSERT, or ignore-existing logic on databases without bulk_load support, use per_page or per_record with `query` — bulk_insert has no duplicate-checking logic. Prefer per_page when the statement can loop `batch_of_records`, and use per_record when the SQL can't be written as one batch statement.
             Set a single value; do not combine types or use the legacy INSERT and UPDATE values.
             per_page statements render against the whole batch (`batch_of_records`) rather than a single record — loop with `{{#each batch_of_records}}...{{record.fieldName}}...{{/each}}`, with the same quoting as `query` (double braces for strings, triple for numbers).
 
@@ -17067,9 +17068,10 @@ components:
               ### UPDATE Operation
               Prompt: "Update inventory counts"
               ```json
-              "queryType": ["per_record"],
-              "query": ["UPDATE inventory SET qty = {{{record.qty}}} WHERE sku = {{record.sku}}"]
+              "queryType": ["per_page"],
+              "query": ["{{#each batch_of_records}}UPDATE inventory SET qty = {{{record.qty}}} WHERE sku = {{record.sku}};{{/each}}"]
               ```
+              Use `"queryType": ["per_record"]` with `"query": ["UPDATE inventory SET qty = {{{record.qty}}} WHERE sku = {{record.sku}}"]` when the SQL can't be written as one batch statement.
 
               ### Run Once Per Page
               Prompt: "Execute this stored procedure for each page of results"
@@ -17087,7 +17089,7 @@ components:
           type: object
           description: |-
             Configuration for batch INSERTs via a multi-row VALUES clause; required when queryType is `["bulk_insert"]` and must not be set otherwise.
-            Only suited to pure INSERTs — for UPDATE, UPSERT, or ignore-existing/skip-duplicates logic, use queryType `["per_record"]` with the `query` field instead.
+            Only suited to pure INSERTs — for UPDATE or UPSERT, use queryType `["per_page"]` (a statement that loops `batch_of_records`) or `["per_record"]` with the `query` field instead, and for ignore-existing/skip-duplicates logic `["per_record"]`.
           x-celigo-ai-guidance:
             - |-
               **CRITICAL: This object is ONLY used when `queryType` is `["bulk_insert"]`.**
@@ -17097,7 +17099,7 @@ components:
               - Pure INSERT operation with NO ignoreExisting/duplicate checking
 
               ❌ **DO NOT SET THIS** when:
-              - `queryType` is `["per_record"]` (use `query` field instead)
+              - `queryType` is `["per_page"]` or `["per_record"]` (use the `query` field instead)
               - Operation involves UPDATE, UPSERT, or ignoreExisting logic
 
               If the prompt mentions "ignore existing", "skip duplicates", or "match on field",
@@ -30620,31 +30622,37 @@ components:
           description: |-
             Selects which files are processed: files matching the filter criteria are exported,
             and non-matching files are skipped entirely before processing begins. Filterable
-            fields come from each file's metadata — most providers expose filename, filesize,
-            and lastmodified (e.g. ["endswith", ["string", ["extract", "filename"]], ".csv"]).
+            fields come from each file's listing entry: the name as `fileName`, the size as
+            `filesize`, and the modified time as `lastModifiedTime` on FTP, SFTP and S3 or
+            `modifiedTime` on cloud-storage folders (`http.type: "file"`)
+            (e.g. ["endswith", ["string", ["extract", "fileName"]], ".csv"]). There is no
+            `lastmodified` key.
           allOf:
             - $ref: '#/components/schemas/Filter'
           x-celigo-ai-guidance:
             - |-
               ## AVAILABLE FILTER FIELDS
 
-              The specific fields available for file filtering are the contained in the `fileMeta` property. 
+              The fields a file filter reads are on each file's listing entry, before the file is
+              downloaded. They are not the records' `fileMeta`, though some names match.
 
               ### Common Filter Fields
 
               These are the most commonly available fields across most file providers:
 
-              1. **filename**: The name of the file (with extension)
+              1. **fileName**: The name of the file (with extension)
                 - Example filter: Match files with specific extensions or naming patterns
-                - Usage: `["endswith", ["string", ["extract", "filename"]], ".csv"]`
+                - Usage: `["endswith", ["string", ["extract", "fileName"]], ".csv"]`
 
               2. **filesize**: The size of the file in bytes
                 - Example filter: Skip files that are too large or too small
                 - Usage: `["lessthan", ["number", ["extract", "filesize"]], 1000000]`
 
-              3. **lastmodified**: The last modification timestamp of the file
+              3. **lastModifiedTime** (FTP, SFTP, S3) or **modifiedTime** (cloud-storage folders): The
+                 last modification timestamp of the file. There is no `lastmodified` key.
                 - Example filter: Process only files created/modified within a specific date range
-                - Usage: `["greaterthan", ["epochtime", ["extract", "lastmodified"]], 1672531200000]` (2023-01-01T00:00:00Z in epoch milliseconds)
+                - Usage (FTP, SFTP, S3): `["greaterthan", ["epochtime", ["extract", "lastModifiedTime"]], 1672531200000]` (2023-01-01T00:00:00Z in epoch milliseconds)
+                - Usage (cloud-storage folders): `["greaterthan", ["epochtime", ["extract", "modifiedTime"]], 1672531200000]`
         backupPath:
           type: string
           description: Path where backup copies of source files are stored before processing.
@@ -31648,7 +31656,10 @@ components:
             - async_helper
         once:
           type: object
-          description: Callback configuration for once exports, used to mark records as exported in the source system after successful processing.
+          description: |-
+            Callback configuration for once exports, used to mark records as exported in the source system after successful processing.
+            Called only while the export's `type` is `once`: an export with no `type` keeps a saved `once` and never calls it, so every
+            run reads every record again (live-verified 2026-10-22).
           properties:
             relativeURI:
               type: string

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@celigo/api-specs",
-  "version": "0.2.175",
+  "version": "0.2.177",
   "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": "89a6949a",
+		"iasCommit": "35c59e78",
 		"generatedAt": "2026-10-22"
 	},
 	"roots": {