Urgent Assistance Needed - Unable to Parse Any Variable Data Across All Make.com Modules

Hi everyone,

I’m reaching out because I’m facing a critical problem with Make.com that’s affecting all my workflows. Suddenly, I can’t parse any variable data in any module, whether it’s input or output. This issue spans across all modules in my account, including Pinterest, Airtable, Google Sheets, OpenAI, and others.

The Core Issue:
No Variable Data Parsing In or Out Across All Modules: Dynamic variable data is not being recognized or processed by any module. This problem appeared abruptly and is consistent throughout my entire Make.com account.
Symptoms I’m Experiencing:
Variables Not Passing Between Modules: Modules like Google Sheets, Airtable, Pinterest, and others are not transferring dynamic data between them. Workflows only function when I use hardcoded values.

Hardcoded Values Work Fine: When I manually input data, everything operates as expected. This suggests the issue is specifically with variable handling, not the modules themselves.

JSON Parsing Failures: The OpenAI module outputs data with unwanted characters like \n. Attempts to clean or parse this data using the JSON Parse module result in a BundleValidationError stating “Missing value of required parameter ‘json’”.

JavaScript Module Errors: Trying to process data using the JavaScript module leads to errors such as ReferenceError: Can’t find variable: content.

Actions I’ve Taken So Far:
Tested with Hardcoded Values: Confirmed that workflows operate correctly with manual data input.

Attempted Data Cleaning and Parsing: Used JSON Parse and JavaScript modules to try and handle the data, but these attempts were unsuccessful due to variable handling issues.

Recreated Data Structures: Tried defining new data structures to properly parse JSON and handle nested objects, but the problem persists.

Impact on My Workflows:
Total Workflow Disruption: All automation involving dynamic data has come to a standstill.

What I’m Seeking:
Understanding the Root Cause: Has anyone experienced a similar issue, or is there a known problem affecting variable parsing in Make.com?

Solutions or Workarounds: Any advice on how to restore variable data parsing functionality would be greatly appreciated.

Additional Information:
No Recent Changes: This issue started without any recent modifications to my account or settings.

Screenshots and Examples: I’m ready to provide detailed screenshots or examples if needed for troubleshooting.

I’m eager to resolve this issue as soon as possible since it’s severely impacting my operations. Any insights or assistance from the community would be incredibly helpful.

Thank you in advance for your support!

Any screenshots?

Alternatively, for technical issues or bugs like this, directly contacting support can often lead to a faster resolution. They have access to your specific account details, scenario and scenario logs, server-side logs, and internal tools and resources, which allows them to investigate more thoroughly than what you have access to. Additionally, sharing sensitive information about your account or scenario might not be suitable for an open forum discussion.

You can open a new ticket here, or if you are unable to login for some reason, you can create another new free account to access the ticketing system (which is only available to logged-in users). Alternatively, you should be able to send an email to helpdesk@make.com and support@make.com and it should create a ticket. After submitting a new ticket, you will receive an automatic confirmation email with the subject “Ticket Created” in the subject. If you do not receive this, try sending the ticket again.

If you manage to get your issue resolved with support, we’d still love to hear about it! Sharing your solution on the forum can help others facing similar problems.

1 Like

Thank you ! I will open a ticket asap

Here is another simple example, in an older scenario (MJ) I am able to simply parse the variable from an increment module to a google sheet, now nothing I do will allow me to do the same in any new scenario regardless of the module. Could the problem lie with my own computer or cache?