Closed darya-mart closed 9 months ago
Hi @mdafokus, I've taken a look into this and after investigating this I found out that it was due to the "service event" change lately. I had to kinda revert this change which means currently we do not send "service events" any longer. However, the payload for Algorithm, Implementation, Data Pool, and Use Case should be consistent again. Please have a look and let me know.
We can leave this issue open until I find a solution for the "service events" ... but we could also create a new issue. whatever you like more :-)
I am closing this issue as we have released the "Service Events" feature and the rest of the events should be consistent. @mdafokus Please feel free to let us know if you notice any unintended behaviour. :)
Current Behavior Topic payload contains inconsistent (compared to frontend) information about entities.
Steps to Reproduce Steps to reproduce the behavior:
"nisqReady": false
in the topic payload"nisqReady": true
in the topic payloadThe same "delayed" behavior appears on any modification, regardless of the field being modified.
Expected Behavior Topic payload contains the same information as displayed in the frontend / stored in the database.