Add support for more timeouts to Nexus operations #595
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.
Add schedule-to-start and start-to-close for Nexus operations
NOTE, before this can be merged the API still needs to be tagged, core changes need to be merged and tests need to be added
Note
Nexus operations
ScheduleNexusOperationCommandAttributeswithschedule_to_start_timeoutandstart_to_close_timeout(read/write/merge + descriptors)Continue-as-new
initial_versioning_behaviortoContinueAsNewWorkflowExecutionCommandAttributesActivities
ActivityExecutionOutcome(result/failure oneof)ActivityExecutionInfoandActivityExecutionListInfomessage typesActivityOptionswithpriorityCommon payloads
Payload.ExternalPayloads(with nestedExternalPayloadDetails.size_bytes) for externally stored payload metadataWritten by Cursor Bugbot for commit ad9e5dc. This will update automatically on new commits. Configure here.