# Duplicate Orders Imported - SFTP into NetSuite **URL:** \ **Category:** Integrator.io\ **Tags:** ftp, integration-app, import, netsuite\ **Created:** [June 12, 2025, 7:42pm UTC](https://connective.celigo.com/t/duplicate-orders-imported-sftp-into-netsuite/4807 "2025-06-12T19:42:16Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![baltazarrocha](https://avatars.discourse-cdn.com/v4/letter/b/3bc359/32.png) [@baltazarrocha](https://connective.celigo.com/u/baltazarrocha)\ **Post date:** [June 12, 2025, 7:42pm UTC](https://connective.celigo.com/t/duplicate-orders-imported-sftp-into-netsuite/4807/1 "2025-06-12T19:42:16Z")
Hello, We noticed today, that our 11:45am MST contained random duplicate orders. Celigo pulls the order file from a SFTP and imports into NetSuite. The source file doesnt contain dupes. It seems something happens during the import process with scripts that is generating duplicates. Here is a sample of some of the dupes. ![A list of sales orders marked as "Pending Fulfillment" includes order numbers, dates, codes, and highlighted text. (Captioned by AI)](https://us1.discourse-cdn.com/flex001/uploads/celigo/original/2X/0/069089ccf8c5c6098937c5f7518f55079d616dc6.png) Here are the two completed Celigo runs during this time. There wernet any errors. This is the first time something like this has happened. ![The image shows a table listing completed tasks with timestamps, completion statuses, and error counts. (Captioned by AI)](https://us1.discourse-cdn.com/flex001/uploads/celigo/original/2X/1/1af7a0ecbd5ddb282d741f4b9a5ede521c16706f.png) Wondering if anyone else has experienced this. Thanks! ---
**Author:** ![baltazarrocha](https://avatars.discourse-cdn.com/v4/letter/b/3bc359/32.png) [@baltazarrocha](https://connective.celigo.com/u/baltazarrocha)\ **Post date:** [June 13, 2025, 3:55pm UTC](https://connective.celigo.com/t/duplicate-orders-imported-sftp-into-netsuite/4807/2 "2025-06-13T15:55:27Z")
Hello everyone, Just an update that we havent seen any more duplicate orders. The issue seems to have resolved itself. Perhaps it was a connection glitch or something similar. But we are good now. Thanks!