#567 Update startedAt timestamp only if not set Pull request opened by pmahindrakar-oss TL;DR Updation of the startedAt timestamp for same taskExecution happens in case of map tasks. So when propeller send the TaskExecutionEvents for each mappedTask, admin records the event and if it finds it to be Running, then calls the addTaskStartedState function which update the startedAt timestamp. This is fine to do in case of regular task but incase of mapped task, each mappedTask status causes an update to startedAt which is incorrect. This PR fixes it by guarding it with if the values is not set Type ☑︎ Bug Fix ☐ Feature ☐ Plugin Are all requirements met? ☐ Code completed ☐ Smoke tested ☑︎ Unit tests added ☐ Code documentation added ☐ Any pending items have an associated Issue Complete description How did you fix the bug, make the feature etc. Link to any design docs etc Tracking Issue fixes flyteorg/flyte#3702 Follow-up issue NA OR https://github.com/flyteorg/flyte/issues/ flyteorg/flyteadmin GitHub Actions: Build & Push Flyteadmin Image GitHub Actions: Goreleaser GitHub Actions: Build & Push Flytescheduler Image GitHub Actions: Bump Version Codecov: 58.43% (-0.04%) compared to 313ac29 ✅ 9 other checks have passed 9/14 successful checks