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
When deleting a submission, we currently raise a message in the Kafka queue named submission.notification.delete.
Currently, this message only contains the v5 submission ID, not the legacyId. The legacyId is also important for the v3 API to be able to handle the submission delete message successfully.
Solution
The message raised to submission.notification.delete must be changed to also contain the legacyId, so that the v3 API (Online Review) can handle the submission delete as well.
Testing
To see submission delete messages, login to https://lauscher.topcoder-dev.com with jcori / appirio123 and select submission.notification.delete as the topic.
Screenshot
The text was updated successfully, but these errors were encountered:
Problem
When deleting a submission, we currently raise a message in the Kafka queue named
submission.notification.delete
.Currently, this message only contains the v5 submission ID, not the legacyId. The legacyId is also important for the v3 API to be able to handle the submission delete message successfully.
Solution
The message raised to
submission.notification.delete
must be changed to also contain the legacyId, so that the v3 API (Online Review) can handle the submission delete as well.Testing
To see submission delete messages, login to https://lauscher.topcoder-dev.com with
jcori
/appirio123
and selectsubmission.notification.delete
as the topic.Screenshot
The text was updated successfully, but these errors were encountered: