Infinite loop in PartialPayloadProcessor when payload size limit is exceeded on first record of a batchDescriptionWhen the Identification Engine processes partial payloads, if the memory limit defined by the property glide.identification_engine.partial_processing_max_fetch_memory_mb is exceeded on the first record of a fetched batch. This causes the query loop to run indefinitely. Partial payloads are fetched in batches (default size: 15). If the cumulative memory from previously fetched records is already near the configured maximum (e.g., 49 MB out of a 50 MB limit), and the first record in the next batch pushes the total over the limit. The result is a thread that never completes, potentially hanging long‑running imports.Affected Versions: Zurich, Australia, Brazil (prior to fix)Steps to Reproduce 1) Run below payload to create partial payloadvar payload = { "items": [{ "className": "cmdb_ci_computer","values": { "ram": "q111211"},"sys_object_source_info": { "source_native_key": "IRE_TOI_PARTIAL_1","source_name": "SERVICENOW","source_feed": "DISK_FEED","source_recency_timestamp": "2019-08-26 13:00:00"}},{ "className": "cmdb_ci_disk","values": { "name": "disk1"}}],"relations": [{ "parent": 0,"child": 1,"type": "Contains::Contained by"}]};var input = new JSON().encode(payload);var output = SNC.IdentificationEngineScriptableApi.createOrUpdateCIEnhanced('SERVICENOW', input, {});gs.print(output);2) Change the property to 'glide.identification_engine.partial_processing_max_fetch_memory_mb' to 03) Rerun below payload and observe the thread is now in an infinite loopvar payload = { "items": [{ "className": "cmdb_ci_computer","values": { "ram": "q111211","name" : "test_partial"},"sys_object_source_info": { "source_native_key": "IRE_TOI_PARTIAL_1","source_name": "SERVICENOW","source_feed": "DISK_FEED","source_recency_timestamp": "2019-08-26 13:00:00"}},{ "className": "cmdb_ci_disk","values": { "name": "disk1"}}],"relations": [{ "parent": 0,"child": 1,"type": "Contains::Contained by"}]};WorkaroundTemporary Workaround:1. Cancel the long‑running transaction as described in KB 0635968. 2. Change the property glide.identification_engine.partial_processing_max_fetch_memory_mb to 100 (or a value larger than the default 50 MB). 3. Reduce the maximum number of partial payload IDs fetched per batch by setting glide.identification_engine.partial_payload_ids_query_limit to 1000 or less (default is 10000). 4. Decrease the cleanup retention period for the cmdb_ire_partial_payload table from the default 30 days to a shorter value (e.g., 7 days) to prevent accumulation of old partial payloads.Permenant Workaround:This issue requires a platform fix — there is no application-level workaround. Upgrade to one of the following patched releases:Zurich Patch 11Australia Patch 4Brazil (or later)Related Problem: PRB2017567