We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
It is possible that a message cannot be read due to various reasons. The S2 standard defines that a ReceptionStatus should be send where the status is set to INVALID_DATA: https://github.com/flexiblepower/s2-ws-json/wiki/Common_messages#receptionstatusvalues In that case, a message_id is impossible to retrieve.
ReceptionStatus
status
INVALID_DATA
message_id
However, in ReceptionStatus the subject_message_id field is required (https://github.com/flexiblepower/s2-ws-json/wiki/Common_messages#receptionstatus). What should we define as the subject_message_id if the message_id is not retrievable and the ReceptionStatus.status is INVALID_DATA?
subject_message_id
ReceptionStatus.status
The text was updated successfully, but these errors were encountered:
For now we are using '00000000-0000-0000-0000-000000000000' in s2-python
'00000000-0000-0000-0000-000000000000'
Sorry, something went wrong.
No branches or pull requests
It is possible that a message cannot be read due to various reasons. The S2 standard defines that a
ReceptionStatus
should be send where thestatus
is set toINVALID_DATA
: https://github.com/flexiblepower/s2-ws-json/wiki/Common_messages#receptionstatusvaluesIn that case, a
message_id
is impossible to retrieve.However, in
ReceptionStatus
thesubject_message_id
field is required (https://github.com/flexiblepower/s2-ws-json/wiki/Common_messages#receptionstatus). What should we define as thesubject_message_id
if themessage_id
is not retrievable and theReceptionStatus.status
isINVALID_DATA
?The text was updated successfully, but these errors were encountered: