This issue was identified as a bug and resolved in the February 2017 release of the RELO plugin and web services. Please update to the latest plugin and web service version to resolve this issue.