We have a JDBC integration where scheduled data source has been creating Case records in Case table. All the records get created by "admin" account. Lately, what we are seeing.. whenever the mid server goes down .. JDBC probe sensor is picking the Input from ecc_queue and generating multiple import sets one after the another and inserting similar ( in this case duplicate) records in the Case Table. This is happening asynchronously. These duplicate Cases are being inserted by mid server ID -m15949. These duplicate records are not at all following the transform map/coalesce rules setup for the integration . So now we have two records being inserted into Case Table ( one by admin and following the transform rules .. and other by M15949 mid server ID and not following any of the transform rules). Any advice?
