@celigo/api-specs 0.2.48 → 0.2.50

package/dist/export.yml

@@ -8455,60 +8455,33 @@ components:
               type:
                 - string
                 - 'null'
-              description: Salesforce formula expression that filters which events are processed; when omitted (stored as `null`), all events for the object are processed. Evaluated inside Salesforce before events are sent, which is more efficient than filtering in a later flow step. Reference only fields that exist on the monitored object; formula functions such as `ISCHANGED(Status__c)` are supported.
+              description: SOQL WHERE-clause condition that filters which record events the listener processes; when omitted (stored as `null`), every event for the object is processed. The Celigo Salesforce package evaluates it inside Salesforce as `SELECT Id FROM <sObjectType> WHERE (<qualifier>) AND Id IN :ids` before anything is sent, so only fields of the monitored object and SOQL comparison syntax apply — Salesforce formula functions are not part of this grammar. A deleted record is never returned by that query, so a listener with any qualifier receives no delete events; leave it unset when removals must trigger the flow.
               x-celigo-ai-guidance:
                 - |-
-                  ## FIELD BEHAVIOR
-
-                  This field provides server-side filtering:
-
-                  - OPTIONAL: If omitted, all events for the object are processed
-                  - Uses Salesforce formula syntax for filtering
-                  - Evaluated before events are sent to the integration platform
-                  - Can reference any field on the triggering record
+                  Write SOQL WHERE syntax only: `field = value`, `!=`, `<`, `>`, `<=`, `>=`, `LIKE`,
+                  `IN (...)`, `AND` / `OR`, parentheses for grouping, `NOT ( <comparison> )`, and
+                  lowercase `true` / `false` literals.
                 - |-
-                  ## IMPLEMENTATION PATTERNS
-
-                  ### Simple Field Comparisons
-                  ```
-                  "Status__c = 'Approved'"
-                  ```
-                  - Processes events only when specific field values match
-                  - Most efficient filtering approach
-                  - Can use =, !=, >, <, >=, <= operators
-
-                  ### Logical Conditions
-                  ```
-                  "Amount > 1000 AND Status__c = 'New'"
-                  ```
-                  - Combines multiple conditions with AND, OR operators
-                  - Can use parentheses for complex grouping
-                  - Allows precise control over which events trigger the integration
-
-                  ### Formula Functions
-                  ```
-                  "CONTAINS(Description, 'Priority') OR ISCHANGED(Status__c)"
-                  ```
-                  - Uses Salesforce formula functions
-                  - ISCHANGED detects specific field modifications
-                  - ISNEW, ISDELETED detect record lifecycle events
+                  Formula syntax is rejected at save with HTTP 422 `Either whereClause expression ...
+                  is invalid ... unexpected token` — observed for `AND(a, b)` argument lists,
+                  `NOT(field)` on a bare boolean, `NOT(ISNEW())`, `ISDELETED()`, and `ISBLANK(field)`;
+                  uppercase `= FALSE` has been rewritten to `NOT(field)` and rejected the same way.
                 - |-
-                  ## PERFORMANCE IMPACT
-
-                  The qualifier is evaluated in Salesforce before sending events:
-                  - Reduces network traffic and processing
-                  - Lowers integration platform load
-                  - More efficient than filtering in a subsequent flow step
-                  - No additional API calls required
-
-                  IMPORTANT: The qualifier is evaluated using the Salesforce formula engine.
-                  Use valid Salesforce formula syntax and reference only fields that exist
-                  on the primary object being monitored.
+                  The rejection surfaces on a real save (a create, or the user's Accept of a staged
+                  update) — dry-run validation does not run the Salesforce-side check, so a staged
+                  card carrying an invalid qualifier passes dry-run and fails at Accept.
+                - |-
+                  `IsDeleted = true` in a qualifier admits nothing — the query runs against the live
+                  record, which no longer exists after a delete, so any qualified listener stops
+                  receiving deletions. To keep deletes flowing, leave the qualifier unset and drop
+                  unwanted events with the export's output filter, accepting that those events still
+                  start a run.
               examples:
                 - Amount > 1000
                 - Status__c = 'Approved'
                 - LeadSource = 'Web' AND Competitor__c = 'Oracle'
-                - ISCHANGED(Status__c) AND NOT(ISNEW())
+                - IsDirect = false
+                - StageName = 'Won' AND ( NOT ( Unresolved_Errors__c >= 1 ) )
             batchSize:
               type:
                 - integer

package/dist/mcp-server.yml

@@ -515,8 +515,11 @@ paths:
         array, `add` works at `/policies/-` or an index, and `replace` works at
         an index or a sub-path such as `/policies/0/config/limit`; `remove` at
         an array index is rejected with 422 `Remove at array index is not
-        supported`. The resulting array is validated as a whole, and an invalid
-        policy rejects the entire patch. `/_networkPolicyId` takes `add`,
+        supported`. The resulting array is validated as a whole, and a policy
+        with invalid `config` (422 `policy_config_invalid`), a missing `name`,
+        or a second policy of the same `type` and `keyResolver` (422
+        `mcp_server_duplicate_policy`) rejects the entire patch.
+        `/_networkPolicyId` takes `add`,
         `replace` (a policy in the same environment, else 422 `invalid_ref`),
         and `remove` to unassign — `replace` with a `null` value is rejected
         with 422 `missing 'value' property`. Setting `/disabled` to `false` is rejected
@@ -2762,17 +2765,21 @@ components:
         server (`keyResolver` `endpoint`) or separately for each OAuth end user
         (`keyResolver` `consumer`); a `quota` caps cumulative calls over a UTC
         calendar DAY, WEEK, or MONTH across every consumer. A call must pass every
-        enabled policy. A rejected call is not executed and receives HTTP 429 with
-        a `Retry-After` header (seconds until the allowance refills or the quota
+        enabled policy. A second policy of the same `type` and `keyResolver` is
+        rejected with 422 `mcp_server_duplicate_policy`. A rejected call is not
+        executed, does not count toward usage, and receives HTTP 429 with a
+        `Retry-After` header (seconds until the allowance refills or the quota
         period resets), an `X-RateLimit-Limit` header, and a JSON-RPC error
         (code -32004) whose message names the policy: `Rate limit exceeded: <name>`
-        or `Usage quota exceeded: <name>`.
+        or `Usage quota exceeded: <name>`. A quota counts only calls accepted after
+        it was added; editing the limit keeps the running count for the current UTC
+        period, and removing then re-adding the quota starts a new count.
       x-celigo-ai-guidance:
         - |-
           Configure one policy per kind — one server-level rate limit, one per-user
-          rate limit (`keyResolver` `consumer`), one quota. The API does not reject a
-          second policy of the same kind; both are then enforced against the same
-          traffic, which makes the effective limit hard to reason about.
+          rate limit (`keyResolver` `consumer`), one quota. A second policy of the
+          same `type` and `keyResolver` is rejected with 422
+          `mcp_server_duplicate_policy`.
         - |-
           A `tools/call` counts against every enabled policy, even when the named tool
           does not exist; `initialize`, `tools/list`, `prompts/list`, and `resources/list`
@@ -2785,9 +2792,10 @@ components:
         - |-
           A rate limit keeps its allowance state when its `limit` is changed, so raising
           a limit right after it tripped admits nothing until tokens refill at the new
-          rate. A quota counts every call the server accepted in the current UTC period,
-          including calls made before the quota was configured — a quota below the
-          period's current count rejects every call until the period resets.
+          rate. A quota counts calls accepted after it was added in the current UTC
+          period; editing the limit keeps the running count, and removing then
+          re-adding the quota starts a new count. Calls rejected by a traffic limit
+          do not consume quota, so raising a quota mid-period takes effect immediately.
       required:
         - type
         - name
@@ -2809,10 +2817,11 @@ components:
             - rate-limit
         name:
           type: string
-          maxLength: 100
+          maxLength: 200
           description: |-
-            Label for the limit, echoed verbatim in the 429 error message that
-            rejected clients receive — name it the way consumers should read it.
+            Required label for the limit, echoed verbatim in the 429 error message
+            that rejected clients receive — name it the way consumers should read
+            it. A missing or empty name is rejected with 422.
           examples:
             - Server-level rate limit
             - Per-user rate limit
@@ -3253,10 +3262,15 @@ components:
           description: |-
             Traffic limits enforced on this server before a tool runs — a
             server-level rate limit, a per-user rate limit, and a usage quota, each
-            optional and independent. An empty array (the default) means unlimited.
-            Always returned; servers saved before traffic limits existed return an
-            empty array. Omitting the field on PUT clears every limit — send the
-            complete array back, or edit it with PATCH.
+            optional and independent. At most one policy per `type` and
+            `keyResolver` is allowed; a second is rejected with 422
+            `mcp_server_duplicate_policy`. An empty array (the default) means
+            unlimited. Always returned; servers saved before traffic limits existed
+            return an empty array. Omitting the field on PUT clears every limit —
+            send the complete array back, or edit it with PATCH. A quota counts
+            calls accepted after it is saved; edits that keep the same `type` and
+            `keyResolver` keep counting from the original add time, and removing
+            the quota (then adding it again) starts a new count.
           x-celigo-ai-guidance:
             - |-
               Leave `policies` empty unless the user asks for a limit — that is today's

package/dist/tool.yml

@@ -31411,60 +31411,33 @@ components:
               type:
                 - string
                 - 'null'
-              description: Salesforce formula expression that filters which events are processed; when omitted (stored as `null`), all events for the object are processed. Evaluated inside Salesforce before events are sent, which is more efficient than filtering in a later flow step. Reference only fields that exist on the monitored object; formula functions such as `ISCHANGED(Status__c)` are supported.
+              description: SOQL WHERE-clause condition that filters which record events the listener processes; when omitted (stored as `null`), every event for the object is processed. The Celigo Salesforce package evaluates it inside Salesforce as `SELECT Id FROM <sObjectType> WHERE (<qualifier>) AND Id IN :ids` before anything is sent, so only fields of the monitored object and SOQL comparison syntax apply — Salesforce formula functions are not part of this grammar. A deleted record is never returned by that query, so a listener with any qualifier receives no delete events; leave it unset when removals must trigger the flow.
               x-celigo-ai-guidance:
                 - |-
-                  ## FIELD BEHAVIOR
-
-                  This field provides server-side filtering:
-
-                  - OPTIONAL: If omitted, all events for the object are processed
-                  - Uses Salesforce formula syntax for filtering
-                  - Evaluated before events are sent to the integration platform
-                  - Can reference any field on the triggering record
+                  Write SOQL WHERE syntax only: `field = value`, `!=`, `<`, `>`, `<=`, `>=`, `LIKE`,
+                  `IN (...)`, `AND` / `OR`, parentheses for grouping, `NOT ( <comparison> )`, and
+                  lowercase `true` / `false` literals.
                 - |-
-                  ## IMPLEMENTATION PATTERNS
-
-                  ### Simple Field Comparisons
-                  ```
-                  "Status__c = 'Approved'"
-                  ```
-                  - Processes events only when specific field values match
-                  - Most efficient filtering approach
-                  - Can use =, !=, >, <, >=, <= operators
-
-                  ### Logical Conditions
-                  ```
-                  "Amount > 1000 AND Status__c = 'New'"
-                  ```
-                  - Combines multiple conditions with AND, OR operators
-                  - Can use parentheses for complex grouping
-                  - Allows precise control over which events trigger the integration
-
-                  ### Formula Functions
-                  ```
-                  "CONTAINS(Description, 'Priority') OR ISCHANGED(Status__c)"
-                  ```
-                  - Uses Salesforce formula functions
-                  - ISCHANGED detects specific field modifications
-                  - ISNEW, ISDELETED detect record lifecycle events
+                  Formula syntax is rejected at save with HTTP 422 `Either whereClause expression ...
+                  is invalid ... unexpected token` — observed for `AND(a, b)` argument lists,
+                  `NOT(field)` on a bare boolean, `NOT(ISNEW())`, `ISDELETED()`, and `ISBLANK(field)`;
+                  uppercase `= FALSE` has been rewritten to `NOT(field)` and rejected the same way.
                 - |-
-                  ## PERFORMANCE IMPACT
-
-                  The qualifier is evaluated in Salesforce before sending events:
-                  - Reduces network traffic and processing
-                  - Lowers integration platform load
-                  - More efficient than filtering in a subsequent flow step
-                  - No additional API calls required
-
-                  IMPORTANT: The qualifier is evaluated using the Salesforce formula engine.
-                  Use valid Salesforce formula syntax and reference only fields that exist
-                  on the primary object being monitored.
+                  The rejection surfaces on a real save (a create, or the user's Accept of a staged
+                  update) — dry-run validation does not run the Salesforce-side check, so a staged
+                  card carrying an invalid qualifier passes dry-run and fails at Accept.
+                - |-
+                  `IsDeleted = true` in a qualifier admits nothing — the query runs against the live
+                  record, which no longer exists after a delete, so any qualified listener stops
+                  receiving deletions. To keep deletes flowing, leave the qualifier unset and drop
+                  unwanted events with the export's output filter, accepting that those events still
+                  start a run.
               examples:
                 - Amount > 1000
                 - Status__c = 'Approved'
                 - LeadSource = 'Web' AND Competitor__c = 'Oracle'
-                - ISCHANGED(Status__c) AND NOT(ISNEW())
+                - IsDirect = false
+                - StageName = 'Won' AND ( NOT ( Unresolved_Errors__c >= 1 ) )
             batchSize:
               type:
                 - integer

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@celigo/api-specs",
-  "version": "0.2.48",
+  "version": "0.2.50",
   "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": "154359a",
-		"generatedAt": "2026-09-23"
+		"iasCommit": "aa43164",
+		"generatedAt": "2026-09-24"
 	},
 	"roots": {
 		"aiagent": 133,