I have a custom activity in journey builder which writes (through REST calls) all records entering it to a web application where the data is stored. When using the update contact activity in the same journey as the custom activity, the update contact values wont be written to the web application at all.
We know that our custom activity works since the original values that already exist in the entry source gets written to our web application. An example; if the entry source has the columns UserId, Address, City and we already have values in UserId and Address-columns but want to update City-column (using update contact activity), our custom activity recieves REST calls containing the UserId and Address but not the updated values of City. The update contact values gets written and works problerly if a new version of the journey is created, when the update contact values is insted part of the entry source.
To clarify how the journey looks: Entry source -> Update contact (we insert values into column) - > Custom activity (write to external web application).
Question: Is it event technincally possible to have a custom activity that writes data externally after a update contact in the same journey?
TL;DR The issue is that the update contact values won't get written to our external web application (through a custom activity) even if we recieve the values that already existed in the entry source.