When continuing as new, the execution timeout is being set as the run timeout on the next run. This change corrects this small typo. The execution timeout cannot be changed on subsequent runs, and therefore doesn't need to be used here at all. The existing spec for continue as new has been updated to cover this case.
When continuing as new, the execution timeout is being set as the run timeout on the next run. This change corrects this small typo. The execution timeout cannot be changed on subsequent runs, and therefore doesn't need to be used here at all. The existing spec for continue as new has been updated to cover this case.