» Published on
A fix has been deployed the 19th of January and after two days of monitoring we conclude that the problem is fixed. We are also working on a longer solution to make the system more robust.
» UpdatedOur matching service (both via API and batch) is currently returning slightly more users than it should, resulting in some user matching positively but then not being able to receive content (response 40105 in the API and "POSTAL" via batch).
» Updated