i’ve been developing this workflow for a client in a sandbox notion: ie. 1) different credential and 2) different database then production level workflow.
when we duplicated the workflow and added in the production credentials (new notion, and new db), it disrupted all prior notion reader flows.
unsure why that would be the case. i had to manually go in, hit refresh, and reattribute the credentials to the sandbox notion.
here’s the error:
e[31m Notion Database Reader Failed!
Could not find database 1ab0966d-9d7c-802d-90cb-f26df2a7335c. Please make sure it exists and that you have granted Gumloop access to it when linking your credentials.e[0m
Hey @michaelraspuzzi! If you’re reporting an issue with a flow or an error in a run, please include the run link and make sure it’s shareable so we can take a look.
Find your run link on the history page. Format: https://www.gumloop.com/pipeline?run_id={{your_run_id}}&workbook_id={{workbook_id}}
Make it shareable by clicking “Share” → ‘Anyone with the link can view’ in the top-left corner of the flow screen.
Provide details about the issue—more context helps us troubleshoot faster.
Hey @michaelraspuzzi – Since the databases have different credentials associated with them, the node parameters will need to be refreshed.
About the other workflows being distruped — that’s definitely odd. Did you replace the default Notion credentials at https://www.gumloop.com/settings/profile/credentials, or did you add the new production credentials separately? If you replaced the default credentials, then yeah, you’d need to refresh the node parameters and workflows using those default credentials would be disrupted.
Regarding the error — can you try deleting and then re-adding the Notion database reader node? After that, under “Show more options” and “Credentials to Use,” just double-check that the correct credentials are selected.
