IMLError "Function 'arrayToObject' finished with error! "value" property in "arr" at index 3 is missing."

[Contabilidade.net]

For about a week, my Pipefy scenarios stopped working. The triggers that are not working are: “Watch new cards”, “Watch moved cards”, “Watch overdue cards”. In fact, the only trigger that is working is the “Run a GraphQl Query”. The error is an IML error: “Function ‘arrayToObject’ finished with error! “value” property in “arr” at index 3 is missing.” Note that this error appears at the first module.

Is there anyone having this problem or has had it before?

I contacted support on December 5th, but I still haven’t received any further information, just that it is under the dev team analysis.

[samliew]

Welcome to the Make community!

1. Screenshots of module fields and filters

Please share screenshots of relevant module fields and filters in question? It would really help other community members to see what you’re looking at.

You can upload images here using the Upload icon in the text editor:

2. Scenario blueprint

Please export the scenario blueprint file to allow others to view the mappings and settings. At the bottom of the scenario editor, you can click on the three dots to find the Export Blueprint menu item.

^{(Note: Exporting your scenario will not include private information or keys to your connections)}

Uploading it here will look like this:

blueprint.json (12.3 KB)

3. And most importantly, Output bundles

Please provide the output bundles of the modules by running the scenario, then click the white speech bubble on the top-right of each module, save the bundle contents in your text editor as a bundle.json file, and upload it here into this discussion thread.

Providing the output bundles will allow others to replicate what is going on in the scenario even if they do not use the external service.

Following these steps will allow others to assist you here. Thanks!

[pnavarro]

Same happening here…

[Michaela]

Hello @Contabilidade.net @pnavarro thank you very much for raising this in the community

I want to acknowledge that this is a known issue on our end. Our dev team has thoroughly investigated this and a fix is ready and waiting for deployment, which is expected to happen very soon.

For more details and updates, you can follow the dedicated community thread here:

Error scenario Pipefy

Hello there, We are having a problem in the Pipefy scenario, it seems that there was some update that now when the scenario gets a Card Info [Pipefy] [Captura de tela de 2023-12-05 15-14-42]

I am genuinely sorry for the frustration and headaches this has been causing. I’m monitoring the situation and will post any updates in the thread above as soon as I learn about them. If you’d like to receive an email notification once the issue is solved, please open a support ticket with us.

Once again, I’m truly sorry for the trouble, and I’m optimistic that the fix will be rolled out shortly. Thank you very much for your understanding and patience.

[Contabilidade.net]

Hi, Michaela.

Thanks for your reply.

What is the deadline for implementing the correction? Our operations are halted for one week, which is detrimental to us.

[Michaela]

Hello @Contabilidade.net @pnavarro

As I mentioned in my previous comment, I was posting updates in the dedicated thread.

Still, I wanted to let you know that the fix is now rolled out

Error scenario Pipefy

Hello everybody @here I was informed that the fix has just been released, and everything should be back to normal. Please take a moment to test and feel free to share your feedback with us. Once again, I apologize for the frustration and inconvenience caused and I truly appreciate your patience during the wait. Please know that had we had a specific time estimate of the release, we would have, indeed, shared it. If you have additional questions or concerns, please reach out to our support tea…

Once again, I am very sorry for any trouble, headaches, and frustrations caused by this.
Thank you very much for your patience and understanding