Closed vanessacalderon closed 6 years ago
@vanessacalderon I tested this SR many times over the weekend and this morning. Reallocation to 311 was working fine. Not sure what was done on your side that broke this reallocation.
I think this issue is related to the particular case's history and not a problem.
If you look through the Activities in this Ticket, you can see we were getting a persistent error due to Internal Comments missing on a Transfer that George did from an Android device that had the fields bug (since resolved). We eventually cleared out this error, resetting the Task so it could be completed again and you did a Reallocate, which did succeed.
So I think that's the background of why this Reallocate action has previous errors of being a Transfer.
Yup, just created a brand new one (15837) and reallocated the outcome. I did not get any errors
Just tried to REALLOCATE, not TRANSFER case 14967 and I get a Bad response in Incapsulate.