Task Changes Slow in Metadata Read Snap
I have been changing task schedules and then trying to read them with the SnapLogic Metadata Read snap. There seems to be a several minute delay in the Read snap noticing the change but the change ap...
Forum Discussion
The error I had was this :
importId is the value I have fetched from the API (in ascending order) and I am joining with other data using inner join and ascending sort order. I interpret this to mean that the error was thrown because the importId of 3210448-USM18 came before 3210448-NYR6 in the join.
I have just twice fetched only the importIds from the API (without doing the join) and both times 3210448-NYR6 came before 3210448-USM18.
In addition, every single value of importId takes the form of 7 numbers followed by a hyphen followed by some other combination of letters and characters. My understanding of sort collation may not be sufficiently advanced so apologies if I'm on the wrong track - given that format I'm not sure how sort collation could have an impact. Even if one collation ignores the hyphen it's the same for every single value?
Thanks again for your thoughts !
I've also been trying to check my union theory by passing the provided offset value to the results. If that offset value is not in increasing order then that would prove the union theory, but so far it's come back fine both times
