Sorting an Issue list results in fewer rows

hi,

So I have a workflow that I use an 'Issue list' as my source - the issue list has 29 rows. If I add a step to sort on the 'Failed Rows' column, my output for that is now 22 rows. No other filtering going on. Tried it on 2 different issues with the same result. However, if I remove the sort on the 'Failed Rows' column I see all 29 rows again.

On version 2.15.2.33 - can someone let me know if its a bug or am I missing something in the logic?

Thanks

Comments

  • Ivan Ng
    Ivan Ng Administrator

    Hi James,

    I wasn't able to replicate your results. The only way I managed to get a quite similar yet different outcome was via adding new issues to the existing list and then going back to the workflow with the issue list as a source and sort step. The sort step doesn't seem to refresh and take in the latest additions in the Issue list. However, yours is showing less. We would probably need more details from you to debug this further. Would you be able to download the Issue list from the Source step and send it to me? Also were there any additions or issues being resolved prior to your 2nd workflow?

    Best regards,
    Ivan Ng

  • Hi, yes there were new issues added to the list (but not all of those new issues were missing on the sort). It was strange seeing the full set of rows on the 'show step results' from the source step and then seeing the smaller list on the next sort step - and I exited and went back into the workflows couple of times. I have gone back into the workflow today and cannot replicate the problem (maybe if I added new issues it would do it?). Perhaps something associated with data cache on the server? What would you like to see from the issue list (I will have to limit some columns as it is production data).

    Thanks

  • Ivan Ng
    Ivan Ng Administrator

    Hi James,

    We found a bug here where the Issue list in the Source step doesn't update the indexes when records are added/removed. This leads to the subsequent steps not picking up the changes in the list. Thanks for highlighting this to us! I'll let you know once the fix is deployed.