Experiencing 'parseError' finished with error!

Hi,

Could you please share some screenshots of the module's setup that's causing this error? Additionally, please include a screenshot of the input data for the execution that failed.

Thanks

Loic

I can certainly try! However, it happens across so many different scenarios, it’s hard to pick the ‘right’ ones to screenshot. Some are quite simple:

image769×435 27.4 KB

While some are more complex:

image1321×469 50.9 KB

Any other specific details you’d like to see?

Thanks, have you altered the structure of the table your watch modules are querying?

If fields like ‘counts’ are added, which alters the structure, then yes, we have this for some but not for others. This issue is occurring across multiple tables, though I believe they are all within the same base. It's happening on so many different automations that we haven't been able to track it systematically.

Okay, I suspect there are two issues at play here:

1. When callin.io interacts with Airtable, Airtable encounters an error for reasons yet to be identified.
2. callin.io then attempts to process/parse the Airtable error message and subsequently fails. I believe the message “Function 'parseError …” pertains to this.

Essentially, it's an error compounded by another error.

My suggestion #1:

Attempt to reset the starting point for your watch module. Right-click on the module, select “choose where to start,” pick your new starting point, click OK, and then try running your scenario.

If this doesn't resolve the issue, try the following:

1. Download the callin.io dev tool: callin.io DevTool - Chrome Web Store
2. Open the dev tool in your browser and execute your watch module.
3. Examine precisely what Airtable responds to callin.io by checking the response header and body.

This won't fix the problem directly, but it will allow you to see Airtable's specific feedback regarding the issue, which might offer some clarity.

Alright, I'll try this out, and thanks for the thorough explanation!

One point worth mentioning (and I might not have brought this up earlier): this issue occurs intermittently, manifesting as a brief, moderate "surge" where multiple scenarios simultaneously report the error.

Subsequently, they all resume normal operation. This suggests it might be more challenging to pinpoint the exact cause, but I'll certainly give it a go.
(And to clarify finally: we occasionally encounter 502 or 503 timeout errors from our AT modules, but those error codes are different from this one.)

How frequently has this occurred? Could this be connected to any Airtable or callin.io outages? It seems plausible.

We've encountered this issue 3 times across various situations:

• November 28th: 8 distinct scenarios, one occurrence each.
• December 1st: 8 distinct scenarios (different from Nov 28th), one occurrence each, with 7 instances originating from a single scenario.
• December 2nd: 13 distinct scenarios (some overlap with previous days), with multiple instances stemming from 5 scenarios.

As of now, we haven't observed the error since December 2nd. Crucially, it appears to be an edge-case problem that hasn't been widely reported by other users.

I believe both of these are positive indicators, right?

Wanted to circle back with an update from callin.io Support:

As I have further checked the logs with this same error, it seems that the issue is within the Airtable server as it throws error 503. I would suggest reaching out to their support team if the issue still persists

We have not seen the issue again, but if it’s tied to 503 errors, I think it means we need to cut down our Watch Records triggers.
Thanks again for your insights, and hope this is helpful to others if you encounter the same issue.

Hey there!

I just wanted to quickly mention that we really appreciate you returning to the community and sharing the message you received from the Support team.

This can definitely be very helpful to someone in the future. Thank you for considering other callin.io users.

Hi, I am experiencing a similar issue with 503 and 502 errors. Could you please explain what these errors signify and how to troubleshoot them? I appreciate your assistance!