Error during json mapping. for multiple connectors

Camunda 8 Topics Discussion & Questions
1

I had an process working last night that wrote to an SNS topic, then this morning with no changes I started getting Error during json mapping.

I ignored this and decided I would try the GraphQL connector and got the same error. Has anyone else seen this error?

2

Hi @Kamau_Washington, welcome to the forums! Are you using the SaaS product or running a self-managed instance? What data are you trying to write to the SNS topic or use with the GraphQL connector?

3

Hi @nathan.loding. I am using the SaaS product, the data I’m trying to to write to the SNS topic is at this point a “Hello World” for subject and message. For the GraphQL I’m doing a simple query

query {
worker(id:“kP7FX1x5JXlthIM9p4fjI”) {
name,
email,
role,
phoneNumber
}
}

It is odd as I can use the Rest Connector just fine. The content type and accept headers are set as well.

Thanks!

4

Are there any additional details that you can share? Any additional logs from the incident in Operate, or your process model perhaps? That error sounds like some data isn’t formatted correctly and the underlying services aren’t able to de/serialize it.

5

Thanks @nathan.loding ! You were right.

So for SNS, I found that it is the expected formatting for the message attribute metadata - vs the typical KVP. They need to b

I’m going to take another stab at the GraphQL one to see if I can track down that error.

1 Like
6

A quick update, I am using Contentful to provide some data and using their GraphQL endpoint for published data, the error arises only when using Auth Bearer tokens, digging a bit more to see if I can pinpoint exactly what the issue is, in case someone else runs into the same thing.