It appears that the mechanism to update the product versions in the customer configuration object store is not working. Customers that have been upgraded recently are still showing an old version of the product. This is causing an impact particularly in the journal API which uses this information to decide which table to write match entries to
Specification
Debug and understand where this problem is coming from. the SUMS Proxy should be intercepting updates to the company record and emitting an event for the organisations API to consume. There is a break in the chain there somewhere
What we know so far (from tests)
Putting a message on the queue manually works fine, this has been tested with a customer that got updated last night. The event was processed and the parameter updated correctly
This was happening because of a misconfigured sums proxy SQS URL. We need to change the parameter name and value so it's a bit more obvious. I've corrected this now and working on remediation
Background context Logged from #11323
It appears that the mechanism to update the product versions in the customer configuration object store is not working. Customers that have been upgraded recently are still showing an old version of the product. This is causing an impact particularly in the journal API which uses this information to decide which table to write match entries to
Specification
What we know so far (from tests)