We are running a large Import Set transformation that is already configured to process data in batches. The transform starts successfully and processes multiple batches, but after a significant number of batches, the transform appears to stall (status remains Running, with no further records being processed and no visible errors).
I would like to understand:
Is there any documented platform limitation (hard or soft) related to:
The total number of batches processed in a single transform run
Long-running import set transformations
Resource or worker constraints that may cause transforms to stop progressing
Are there known behaviors or thresholds (e.g., memory, workers, transaction time, database locking) where a batched transform may appear stuck even though no errors are reported?
Does ServiceNow recommend any maximum batch size, total record count, or execution pattern for large-volume transforms to avoid this behavior?
The transform map contains a simple script that converts epoch to glideduration and the target table is a custom table that contains two referenced fields. We are trying to determine whether this behavior is expected for very large imports or if there is a recommended architectural approach for long-running, batched transformations.
