@celigo/api-specs 0.2.5 → 0.2.7

package/dist/connection.yml

@@ -2445,7 +2445,15 @@ components:
             autoRecoverRateLimitErrors:
               type: boolean
               default: true
-              description: When true, the connection automatically backs off and retries when it encounters rate-limit errors from the target system.
+              description: |-
+                When true, rate-limit errors from the target system trigger automatic recovery: concurrency
+                drops to 1, the rate-limited requests are retried with doubling waits (1 to 1024 minutes,
+                after which the flag switches itself off), and concurrency climbs back toward
+                `targetConcurrencyLevel`. While true, `concurrencyLevel` is platform-managed and writes to
+                it are ignored — `targetConcurrencyLevel` is the lever.
+              x-celigo-ai-guidance:
+                - To change throughput while this is true, write `targetConcurrencyLevel`; a `concurrencyLevel` write returns 200 and changes nothing.
+                - Turning it on copies `concurrencyLevel` into `targetConcurrencyLevel`; turning it off copies the target back into `concurrencyLevel` and unsets the target.
             enableMicroBatchForOneToMany:
               type: boolean
               default: true
@@ -3722,16 +3730,17 @@ components:
             Higher values increase throughput but may trigger API rate limits.
             Set this based on the target API's rate limit documentation.
             Values above the account's licensed maximum (25 standard, 50 with an Environments license) are silently clamped down.
+            Platform-managed while `autoRecoverRateLimitErrors` is true — writes are ignored; set `targetConcurrencyLevel` instead.
           minimum: 1
           maximum: 50
           default: 25
         targetConcurrencyLevel:
           type: number
           description: |
-            Target concurrency level for auto-scaling. The system automatically adjusts
-            concurrency between 1 and this value based on rate limit feedback.
+            Ceiling the platform climbs back to after rate-limit recovery, in steps of 25% of this value.
+            Writing it also sets `concurrencyLevel` to the same value and stops any recovery in progress.
 
-            Only relevant when autoRecoverRateLimitErrors is enabled on the connection.
+            Honored only while `autoRecoverRateLimitErrors` is true; ignored, and unset, when it is false.
           minimum: 1
           maximum: 50
           examples:

package/dist/flow.yml

@@ -5333,10 +5333,18 @@ components:
             - false
         autoResolveMatchingTraceKeys:
           type: boolean
-          description: When true, new errors with trace keys matching existing open errors are auto-resolved.
+          default: true
+          description: |-
+            When true, a new error for a record whose trace key already has open errors on the same step
+            auto-resolves the older ones, a later success for that record auto-resolves its open errors,
+            and errors classified `intermittent` are retried automatically — up to four attempts, the
+            first about 30 minutes after the error.
           examples:
             - true
             - false
+          x-celigo-ai-guidance:
+            - Both behaviors hang off this one flag — off means repeated failures of a record stay open and intermittent errors get no automatic retries; never turn it off as a fix for "duplicate" errors (those come from the destination, not from trace keys).
+            - Intermittent auto-retry does not depend on the trace key — errors with a blank trace key are scheduled and retried the same way; a blank key only loses the duplicate collapse.
         isAbstract:
           type: boolean
           description: |-
@@ -6102,13 +6110,18 @@ components:
         classification:
           type: string
           description: |-
-            Category assigned by the platform (or a user) to this error — drives auto-retry and reporting.
-            Empty when unclassified.
+            Category the platform derives from the error's code, message, and source — read-only, never
+            set by users; `intermittent` errors are retried automatically while the flow's
+            `autoResolveMatchingTraceKeys` is on. Absent when nothing matched with confidence. The value
+            set is the `classification` dimension of the errors filter metadata.
           examples:
             - intermittent
+          x-celigo-ai-guidance:
+            - Read the classification off the record; never infer it from the message text — the classifier is heuristic and identical messages can classify differently.
+            - There is no setting, mapping, hook, or API that changes a classification; a wrong one is a Celigo Support matter.
         classifiedBy:
           type: string
-          description: '`auto` when the platform classified it, or a user id / email when a human did.'
+          description: '`auto` on every classified error; absent on unclassified ones.'
           examples:
             - auto
         reqAndResKey:
@@ -6140,11 +6153,14 @@ components:
           type: string
           format: date-time
           description: |-
-            When the platform is scheduled to auto-retry this error. Populated on `classification:
-            intermittent` errors (the platform retries with exponential backoff up to a cap). Absent on
-            errors that won't be auto-retried.
+            Present while the platform is auto-retrying this `intermittent` error. On a first-occurrence
+            error it is stamped about a minute after `occurredAt` and is not the first attempt time (that
+            runs roughly 30 minutes out); on the error a failed attempt opens, it is the next scheduled
+            attempt. Absent once the attempts are exhausted and on errors that are not auto-retried.
           examples:
             - '2026-01-15T09:35:00.000Z'
+          x-celigo-ai-guidance:
+            - Presence answers "is this error in auto-retry mode?"; the value is a real schedule only after at least one attempt has run.
         tags:
           type:
             - array

package/dist/job.yml

@@ -1707,8 +1707,16 @@ components:
             Omitting `time_gt` does not mean "all history" — the endpoint falls back to the dashboard's
             default window (approximately the last 24 hours), and runs older than that silently drop out
             of every aggregate. Send `time_gt` (epoch milliseconds) explicitly for any other range.
+
+            `time_lte` must not be later than the current time: a future value is rejected with
+            `400 invalid_filter_request_body` (unlike `POST /v1/jobs/current`, which accepts it). Omit
+            `time_lte` to end the window at now. When both bounds are sent they must be at least one hour
+            apart (`time_lte - time_gt >= 3600000`), or the request is rejected with
+            `400 invalid_time_filter`; a window with `time_gt` alone has no minimum span.
           x-celigo-ai-guidance:
             - Always send an explicit time_gt matching the window you intend to report, and never present the aggregates as covering a longer period than the time filter you sent. Without time_gt the default window (~24 hours) applies — an empty result then means "nothing ran recently", never "no runs exist".
+            - For a window that runs through the present, omit time_lte rather than computing an end bound — a value even seconds ahead of the server clock (a rounded-up "now", end of today) fails the whole request with 400 invalid_filter_request_body.
+            - A closed window narrower than one hour cannot be queried; widen time_lte to time_gt + one hour (and say so when reporting) rather than sending the narrower range.
             - A flow absent from stats[] had no runs in the window; it does not mean the flow does not exist. numOpenError counts errors open NOW, which may predate the window.
     FlowRunStatsEntry:
       type: object

package/dist/tool.yml

@@ -4883,7 +4883,15 @@ components:
             autoRecoverRateLimitErrors:
               type: boolean
               default: true
-              description: When true, the connection automatically backs off and retries when it encounters rate-limit errors from the target system.
+              description: |-
+                When true, rate-limit errors from the target system trigger automatic recovery: concurrency
+                drops to 1, the rate-limited requests are retried with doubling waits (1 to 1024 minutes,
+                after which the flag switches itself off), and concurrency climbs back toward
+                `targetConcurrencyLevel`. While true, `concurrencyLevel` is platform-managed and writes to
+                it are ignored — `targetConcurrencyLevel` is the lever.
+              x-celigo-ai-guidance:
+                - To change throughput while this is true, write `targetConcurrencyLevel`; a `concurrencyLevel` write returns 200 and changes nothing.
+                - Turning it on copies `concurrencyLevel` into `targetConcurrencyLevel`; turning it off copies the target back into `concurrencyLevel` and unsets the target.
             enableMicroBatchForOneToMany:
               type: boolean
               default: true
@@ -6160,16 +6168,17 @@ components:
             Higher values increase throughput but may trigger API rate limits.
             Set this based on the target API's rate limit documentation.
             Values above the account's licensed maximum (25 standard, 50 with an Environments license) are silently clamped down.
+            Platform-managed while `autoRecoverRateLimitErrors` is true — writes are ignored; set `targetConcurrencyLevel` instead.
           minimum: 1
           maximum: 50
           default: 25
         targetConcurrencyLevel:
           type: number
           description: |
-            Target concurrency level for auto-scaling. The system automatically adjusts
-            concurrency between 1 and this value based on rate limit feedback.
+            Ceiling the platform climbs back to after rate-limit recovery, in steps of 25% of this value.
+            Writing it also sets `concurrencyLevel` to the same value and stops any recovery in progress.
 
-            Only relevant when autoRecoverRateLimitErrors is enabled on the connection.
+            Honored only while `autoRecoverRateLimitErrors` is true; ignored, and unset, when it is false.
           minimum: 1
           maximum: 50
           examples:

package/package.json

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

package/schemas.json

@@ -1,8 +1,8 @@
 {
 	"provenance": {
 		"repo": "celigo/integrator-api-specs",
-		"iasCommit": "20eb548",
-		"generatedAt": "2026-09-09"
+		"iasCommit": "ffdb923",
+		"generatedAt": "2026-09-10"
 	},
 	"roots": {
 		"aiagent": 121,