Python Module Parsing Error despite valid JSON

Hi Team

Since I work on metafields JSON received from Shopify, some of these JSONs can be pretty large. I am using Code (Python) by Pabbly to parse them and generate appropriate output. It is working well in most of the cases.

However, in one particular instance, this (Code Pabbly) failed. I am getting an error "unexpected character after line continuation character (, line 3)" which is inside the JSON. I have double checked and this appears to be a valid JSON - it is anyway coming directly from Shopify. You can check webhook response D of the workflow mentioned below by me to investigate the same.

Please let me know if you need any other inputs to check this out.

Hello @sunstorm,

Please allow us some time to look into the issue and as soon as we have any further updates we will get back to you.

Hi Team - A gentle reminder

Hello @sunstorm,

Upon checking now for Response D, the code by Pabbly action seems to be working fine. Please check it on your end and let us know if it works fine for you.

Hi Team

Just checked. Response D is indeed working fine now.

However, Response C is still throwing an error in Step 5. Code (Python) by Pabbly

Hello @sunstorm,

Thank you for bringing this to our attention. Our team has thoroughly investigated the issue and attempted multiple workarounds to resolve it. However, the problem appears to stem from the response received in Step 3 of your workflow.

We recommend reaching out to Shopify Support for further clarification, as the JSON response seems to contain certain characters that are causing it to break. They should be able to provide insights into the issue and possible solutions.

Let us know if you need any further assistance!

Hi Team

Figured out a workaround. The issue was happening mainly due to one of the "rich text" metafields containing multiple paragraphs. I wasn't using it anymore and so have chosen to delete it from my store. That appears to have resolved the issue for now.

Hello @sunstorm,

Thanks for adding the update.

If you face any further difficulties in the future, please feel free to reach out to us.