Issue with One-to-Many POST Call and Response Mapping

Integrator.io
1

Hi All,

I've encountered a strange issue when using a POST (or GET) call with a one-to-many relationship and response mapping.

If one of the records in the call fails (e.g., the second record), and I manually fix it afterwards, the first record — which was already processed successfully (should have responded data ready to go) but does not show the expected response mapping.

Has anyone experienced the same problem before or know the way to fix it?

Cheers,
Jacky

3

I was able to reproduce this and it’s quite an ugly bug. I’ll log this and see if we can prioritize.

Example of no error happening along the way:

{
  "array": [
    {
      "number": "1",
      "lookupResults": [
        {
          "good": "T"
        }
      ]
    },
    {
      "number": "3",
      "lookupResults": [
        {
          "good": "T"
        }
      ]
    }
  ]
}

Example where first record worked, second record failed, then I retried the second so it was successful:

{
  "array": [
    {
      "number": "1"
    },
    {
      "number": "3",
      "lookupResults": [
        {
          "good": "T"
        }
      ]
    }
  ]
}
4

Thanks, it took me a while to find out it's a bug at the Celigo end.

I’m not sure how you ran your test. Do you mind showing me how you did it? So, if I encounter the issues later on, I can use the same method you did to debug the bug more efficiently.

5

Here you go. The lookup is set to fail when the number = 2, so if you run it normally and then edit the retry data of the error to number = 3, enabling debug logs on the last step, you can see the behavior. If you set the number = 1 and 3 on the first step, then no failure occurs, and you can see the full successful response on the last step.

image
image3042×774 125 KB

6894c26c8d5e9cad9ac621c8.zip (4.0 KB)

6

Thanks, that is the same thing I did at my end before… I thought you had a different way to debug it.

Good to know I’m doing the same thing as you do.. So this bug will be fixed shortly?

7

I’ll have to wait until engineering analyzes it. If you want to make a support ticket, they can link your ticket to our internal ticket so you can get updates.

8

Hi Tyler,

I already have a support ticket and Lan told me to post the issues in Connective to have a fast response.

The ticket is 256231. Can you help me or tell me how to link it. So I can get updates?

Cheers

Jacky

9

@lanreyes will link it and after that you’ll get automated updates. I’ll ping him as well.

10

Hi Tyler, the ticket has been linked to Jira and assigned to Product. We will update Jacky on the progress of this case.

1 Like
11

@jackymao this should be fixed in the release next week.