Why am I Getting Constant Null Responses from Supabase Despite Correct Outputs and Authentication?

Help
1

This topic was automatically generated from Slack. You can find the original thread here.

Getting constant null responses from Supabase where the output should exist

Have contacted Supabase, confirmed it’s not an authentication error, and they mentioned to move away from Pipedream

What’s going on

This has happened to all my businesses (different Supabase accounts). The flows never had an issue for months, and now all are failing on a simple Supabase step?

2

could you do me a favor and share your workflow with Support and then send me a DM with the workflow URL? I’d like to take a look to see if I can help

3

Submitted

4

Thanks, taking a look right now

5

I was able to repro on one of our own Supabase tables, looking into it more and will submit a patch to fix, will keep you updated

6

Thanks Greatly appreciated

7

I shipped a version with much better error handling / verbosity, as well. When that’s deployed in a few minutes, do you mind if I update and test the action in the workflow you shared?

8

the new version is out, do you mind if I update that action to this latest version and test it?

9

Yes that’s fine Thanks

10

It looks like the query exceeds the default timeout of 8 seconds set on Supabase’s side (if you edit the workflow and take a look at my latest test, you’ll see the error).

Do you want to try increasing the default timeout of those calls, or would you want to set the timeout as an optional param on the Pipedream side (which I can do now for you)?

11

I have changed it to 15seconds on Supabase

However I never ran into an issue with the 8second timeout, even when manually testing a Supabase step?

Not sure if that’s the error