×

You're using an outdated browser

For a better experience, keep your browser up to date. Check here for the latest version.

Manual

Incompatible message format

Matthias Gaiser

Matthias Gaiser Last update: Nov 3, 2016

Symptoms

An issue does not get synchronized and appears in the troubleshooting section with the category 'Incompatible message format' and the message, e.g. 'Can not deserialize instance of java.lang.Integer out of START_OBJECT token at [Source: N/A; line: -1, column: -1]'.

Cause

The message format has been changed between the time of sending and consuming the change. This might be due to the following reasons:

  • You've changed a field mapping from Passthrough Value Mapping to Priority Value Mapping or vice versa.
  • You've changed a field mapping from Passthrough Value Mapping to Single/Multi/Cascading Select Value Mapping or vice versa.
  • The same error might occur for other cases where you've changed the mapping for a field.

Resolution

Please perform a resync for the affected issue(s) from the sender project to the receiver project.

2x3.7
We use cookies to create a secure and effective browsing experience for our website visitors and to understand how you use our site (i.e. Google Analytics). For more information: click here.
Ok