When 'start_to_close' Times Out, Last Successful Result Is Null

[tomatopunk]

Version of Cadence server, and client(which language)
This is very important to root cause bugs.

• Server version: 3.35.2
• Client version: v0.19.0
• Client langauge: go

Describe the bug
When the Workflow 'start_to_close' Times Out, the Last Completion Result Cannot Retrieve the Last Successful Outcome"
To Reproduce
Is the issue reproducible?

• [Yes]

Steps to reproduce the behavior:
A clear and concise description of the reproduce steps.

1. decision timeout
2. after execute no result

Expected behavior
obtain the progress of previous successful runs

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context

      "executionStartToCloseTimeoutSeconds": 60,
      "taskStartToCloseTimeoutSeconds": 60,
      "continuedExecutionRunId": "ce8960e2-9db3-481e-acdb-d2c6d58d1f32",
      "initiator": "CronSchedule",
      "continuedFailureReason": "cadenceInternal:Timeout START_TO_CLOSE",
      "continuedFailureDetails": null,
      "lastCompletionResult": null,
      "originalExecutionRunId": "2b2e14e1-513a-4cc2-9592-7cbbfe9818b1",
      "identity": "",
      "firstExecutionRunId": "a7412fec-9bd9-4f84-a049-36de9b0674b2",
      "retryPolicy": null,
      "attempt": 0,
      "expirationTimestamp": null,
      "cronSchedule": "*/1 * * * *",
      "firstDecisionTaskBackoffSeconds": 60,
      "memo": null,