Closed
Description
Think of this scenario:
- I create a challenge in workmanager. Status is New
- That gets to the legacy challenge processor, it doesn’t create it because it’s status is New.
- Legacy challenge resource processor also gets a message to add the user on that challenge as a manager/observer, whatever… But it’s going to retry 3 times to find that legacy id and fail…
Solution
When the legacy challenge processor decides to create the challenge on legacy, it will fetch existing resources and post to kafka. It’ll basically re-post everything again so the legacy challenge resource proc process those