mastermanuandGitHub 54ea7ba85c Sets ContinueAsNewInitiator value to "UNSPECIFIED" instead of "WORKFLOW" for user-created workflows (#753) ...

For Workflows that are explicitly started (e.g. not cron, continue-as-new, or retry-based), we were setting the ContinueAsNewInitiator type to "WORKFLOW." This can be quite confusing to the user, so we have instead switched it to "UNSPECIFIED."

In addition to updated unit tests, and running integration tests, we also inspected real-time event values for retry, cron and continue-as-new scenarios to validate proper behavior. We also scanned Temporal Server logs to make sure there was no unexpected behavior due to this change.

This is a low-risk change

2020-09-22 22:06:41 -07:00

..

defaults.go

Sets ContinueAsNewInitiator value to "UNSPECIFIED" instead of "WORKFLOW" for user-created workflows (#753)

2020-09-22 22:06:41 -07:00