MySQL row updates not working - works when run module only

Hey

So if I hard code every variable in the module and click run module only it adds the row fine.

If however I run the scenario it says its added the row but the row does not add to MySQL database.

Any ideas why this could be?

I’ve hardcoded every value to rule out any values so in theory it should be the exact same if run module only or the scenario.

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, Input/Output bundles

Please provide the input and output bundles of the trigger/iterator/aggregator modules by running the scenario (or get from the scenario History tab), then click the white speech bubble on the top-right of each module and select “Download input/output bundles”.

A.

Save each bundle contents in your text editor as a bundle.txt file, and upload it here into this discussion thread.

Uploading them here will look like this:

module-1-output-bundle.txt (12.3 KB)

B.

If you are unable to upload files on this forum, alternatively you can paste the formatted bundles in this manner:

  • Either add three backticks ``` before and after the code, like this:

    ```
    input/output bundle content goes here
    ```

  • Or use the format code button in the editor:

Providing the input/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!

samliewrequest private consultation

Join the Make Fans Discord server to chat with other makers!

Could it be an IP whitelisting issue? If you use run module only is it doing the connection from my IP? Where as if I run the scenario is it using a Make IP? The Make MySQL article mentions IPs to whitelist but then theres nothing below the text.

Unlikely.

Nope, it still runs from Make.

I can attach the blueprint but its going to be pretty useless because it uses custom API calls and I can’t include the APIs and they are pulled from Notion.

Here is an example output bundle though showing the row has been affected yet for some reason it does not commit to the database yet the exact same does if I run the module only.
blueprint.json (179.9 KB)

[
    {
        "fieldCount": 0,
        "affectedRows": 1,
        "insertId": 82402,
        "info": "",
        "serverStatus": 3,
        "warningStatus": 0
    }
]

I think I managed to solve it, I think using “Manage data within the shared transaction” was the issue, I turned this off and it seems to now be working.

You might have to turn on auto-commit in your scenario settings

Screenshot_2024-06-29_190628

Or you might not be seeing the warnings, if this is turned off

Screenshot_2024-06-29_190629

If there is no new information, you might need to contact Make support, since the data in your scenario is sensitive.

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).

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.

Join the Make Fans Discord server to chat with other makers!