This could happen in the following situation:
- You have a two-sided reconciliation where one side comes from a Data Prep process
- You have manually created a snapshot on your Data Prep process
- You have then manually triggered a run on your two-sided reconciliation
- Your two-sided is then run automatically via SFTP submissions
When the above conditions are met, you will notice that on the Data Prep side, the automated run will include the manually created snapshot as well as the snapshot that was created off the back of the SFTP submissions.
The reason this happens is because the manually created snapshot remains in an outstanding state, meaning Duco will merge it with subsequent submissions and include it in the next automated run.
To clear this, you can submit a file to the other side through SFTP to trigger an automatic run and mark the run as failed.