#3344 Skip get_node_execution_data if data missing Pull request opened by wild-endeavor ## Why are the changes needed? Propeller correctly skips nodes in failure scenarios, and abort scenarios. In these instances, there is no node execution data to pull. Flyte Remote needs to skip these nodes when syncing. ## What changes were proposed in this pull request? Catch the exception raised by the

get_node_execution_data

endpoint. ## How was this patch tested? Tested against user's failure scenario. ### 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 bug fix that enhances the Flyte Remote functionality by adding exception handling for node execution data retrieval. If data is not found, the process will skip the node instead of raising an error, allowing for graceful handling of failure scenarios. flyteorg/flytekit