Activity Execution Info to support checking if heartbeat details from previous attempt are available #41
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
Currently, we offer
heartbeatDetails(as:)method to retrieve the activity details of an activity execution. If it's the first attempt, this method fails with an ArgumentErrorMismatched number of values and payloadsas there are no heartbeat details available. The user has no way to differentiate between no heartbeat details being available or that they did indeed supple the wrong amount of payload types.Modifications
We have
heartbeatDetails(as:)return an optional tuple instead, so users can check if there are heartbeat details available from previous activity attempts.Test Plan
Augmented existing unit tests to check activity details to be present or not.