Hi @MF-60085, Thanks for the data! We've found that the root cause this time is due to some duplicate rows in the original table, which for some reason was not created with any uniqueness constraints. We'll get this fixed in a prerelease version within a day or two.

@Dan_Woolf Sounds good, thanks for the response.

Hello; this will probably be the fastest route to fix things -- https://docs.inedo.com/docs/desktophub/troubleshooting