I’m very frustrated with this ongoing issue that’s completely stopped my business. The turnaround time for fixing a known error is unacceptable. I understand Notion’s update may require some adaptation, but this situation is untenable. I pay for Zapier and can’t do essential daily tasks. This is a significant waste of time and resources, with no updates or estimated resolution.

Has anyone found a way to help me resume my business activities?

I am experiencing the same issue. I have tried the following and have been unsuccessful in fixing this error:

• Disconnecting and reconnecting notion
• Updating the Zap to use Notion v 2.20.3
• Validating all fields are mapped

The most interesting part is that the notion database id that “cannot be found” in the error doesn’t match the notion database ID that it is trying to create the page in. The database ID in the error doesn’t seem to exist in our org. I also verified the notion database selected is the correct one AND that the database id displayed in the configure step of the zap is correct.

Hi ​@alvinliang, ​@Korey, ​@VatcheM, ​@jared103, ​@alfred88, ​@NBRealty and ​@thamersma 👋

I’m really sorry for all the disruption caused. I know this issue has put a lot of workflows on pause and can understand how stressful this must be. I wish I had a clear timeline for you all, but what I can share is that this is a high priority and our engineers are actively working to resolve it as quickly as they can. I’ll make sure the team receives the feedback folks have shared here so they can fully understand the impact and work on improving how we handle issues like this moving forward.

I’ve added everyone who’s not already on the impacted list, so you’ll all get notified once it’s resolved. Not sure if everyone's seen that there was a related Notion bug that got closed earlier today, but that seems to have been only a partial fix. Some issues with data sources remain, and we’re working to get those resolved as well:

Just wanted to flag that in case it affects anyone here too.

We’ll keep this thread updated with any news on this end. If you see any new symptoms or changes (error messages, behavior shifts etc.), please post them here so I can flag them to our engineers or reach out to our Support team directly to let them know. Thanks so much for your continued patience while this is being worked on.

Hey everyone, a new version of the Notion app was recently rolled out to help fix the issues across multiple Notion triggers and actions. The bug report for the issue being discussed here is still open but I wanted to share this quick update here to keep you all in the loop.

If things are working again for you with the newer version, please do let us know 🤞

This change has not really improved our situation, the Notion app fails to load a lot now while trying to test this.

Sorry to hear that ​@Korey. Can you confirm which Notion action you’re seeing that error on?

It times out on the “Update Data Source Item”. Just before that we have a “Retrieve a Page” step which loads fine. If I try to change or configure it, it just results in another timeout again.

Additionally, we also get “Error: Failed to fetch needs for step _GEN_1759260785981. A network error occurred.” on the next step (also a “Update Data Source Item” step).

​@SamB the update to 2.20.5 has resolved the issue for me. Here are the steps I took for others to try:

1. Edit zap
2. In "Setup" during the Notion step
   1. In the "App" section -> click "change" -> search for "Notion" -> 
   2. In the "Account" section" -> click "change" -> ensure you are selecting an account with v2.20.5. You may need to reconnect Notion to Zapier to see this. I reconnected by
      1. Removing Zapier from the connections menu in Notion
      2. Reconnecting Zapier inside one of my Zaps
3. From there, my test records were successfully creating Notion database pages again

this is now working for me. v.2.20.3 was broken. the newest version that works is v2.20.5

It times out on the “Update Data Source Item”. Just before that we have a “Retrieve a Page” step which loads fine. If I try to change or configure it, it just results in another timeout again.

 

Additionally, we also get “Error: Failed to fetch needs for step _GEN_1759260785981. A network error occurred.” on the next step (also a “Update Data Source Item” step).

 

 

This is also happening to my zaps. I’ve corrected all of my other zaps after yesterday’s update and they’re running fine so far. However this Update Data Source Item one I’m getting the following error. This is using the Notion v2.20.6 version:
 

Thanks so much for all the updates here ​@Korey, ​@thamersma, ​@alfred88 and ​@VatcheM! 🤗 I’m glad that it’s working again for some of you at least. The bug report is still open while our engineers continue working to address these new errors. I’ll let you know here if I get any updates in the meantime. 

Hi all 👋

The bug report regarding the “Could not find database with ID...” errors is still open. However, a different bug report (related specifically to timeout errors) was closed on Friday. The fix that was implemented for that issue also included updates to address other related problems.

Here’s the key details from the email notification that was sent about the recent fix:

Just wanted to confirm directly with folks here, has the latest version resolved both the “Could not find database with ID...” and “We can’t retrieve information from this step right now...” errors for you? Please let me know!