#3340 Add default sort_by to iterate_node_executions Pull request opened by Sovietaced ## Tracking issue Closes #6676 ## Why are the changes needed? Limit & offset pagination only works when the iteration order of the values from the database is deterministic. Without this change in some circumstances it is possible for some nodes to be omitted from the result which is very frustrating/confusing for users. ## What changes were proposed in this pull request? Adds a configurable sort_by option and defaults to ordering nodes by their

created_at

timestamp in ASC order. ## How was this patch tested? Tested locally in our environment. ### Setup process ### Screenshots ## Check all the applicable boxes • I updated the documentation accordingly. • All new and existing tests passed. • All commits are signed-off. ## Related PRs ## Docs link https://bito.ai#summarystart| ### Summary by Bito This pull request introduces a new configurable

sort_by

option for the

iterate_node_executions

and

iterate_task_executions

functions, enhancing pagination reliability by sorting results deterministically by

created_at

. This modification improves user experience by ensuring clearer and more consistent data retrieval. flyteorg/flytekit