Internal Server Error when saving scenario with Notion "Update a Data Source Item" module

Questions
,
1

:bullseye: What is your goal?

Sync 3 Notion databases (Tasks, Projects, Collaborations) to Google Calendar using Search Objects → Router → Create/Update GCal Event → Update a Data Source Item.

:thinking: What is the problem & what have you tried?

Every time I save the full scenario after configuring the “Update a Data Source Item” modules, I get Internal Server Error. This has happened across 4 separate rebuilds. Individual module configs appear to save fine, but the whole-scenario save always fails with a 500. I’ve tried re-importing the blueprint from scratch multiple times. The Search Objects modules (v1) save fine — the issue is specifically when the scenario also contains “Update a Data Source Item” modules.

:clipboard: Error messages or input/output bundles

Internal Server Error (500) — appears when clicking Save on the full scenario. No additional detail provided by Make UI.

5

Hi @thecravenfoodie

Internal Server Error (500) probably happened because of a structural conflict between your “Update a Data Source Item” module and the newly mapped variables from your Notion v1 modules. Did you import the blueprint? A data type or reference mismatch is most likely causing the issue when http://make.com engine tries to compile your entire blueprint.
Did you notice the specific module that caused the error when you saved the entire scenario?

To troubleshoot this please duplicate the scenario as many times as the modules in the scenario. If there are 5 modules duplicates it 5 times and for each of the duplicates delete a unique module and then try to save every duplicate short of a module. The ones that gets saved will probably give you a clue of the module causing the error or the modules conflicting.

From that point check the complicated module’s data source, data types, parameters, where it sends data to, or try to rebuild the same module from scratch especially if the blueprint was imported.

Delete the problematic module(s) and try to add them from scratch. Try to save everything step by step even if it shows uncompleted parameters click the “Save Anyway” when you hit that particular action that caused the mismatch the saving will fail.