You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Marker commands should never be sent to server with an empty marker name.
Actual Behavior
That happened
Steps to Reproduce the Problem
Unclear. Some user workflows were seen encountering this error on workflow completion:
BadRecordMarkerAttributes: MarkerName is not set on RecordMarkerCommand.
From what I could tell looking at the code briefly, the only way it seemed like this might happen is if the marker command was constructed while replaying was true, and then it later became false and sent off the command.
Specifications
This was definitely Java SDK, which we determined by seeing the stack trace query. Not clear which version. Java needs to do #1838
The text was updated successfully, but these errors were encountered:
Expected Behavior
Marker commands should never be sent to server with an empty marker name.
Actual Behavior
That happened
Steps to Reproduce the Problem
Unclear. Some user workflows were seen encountering this error on workflow completion:
BadRecordMarkerAttributes: MarkerName is not set on RecordMarkerCommand.
From what I could tell looking at the code briefly, the only way it seemed like this might happen is if the marker command was constructed while replaying was true, and then it later became false and sent off the command.
Specifications
This was definitely Java SDK, which we determined by seeing the stack trace query. Not clear which version. Java needs to do #1838
The text was updated successfully, but these errors were encountered: