This topic was automatically generated from Slack. You can find the original thread here.
Seems to be an issue with Supabase on Pipedream - it completes the step but does not show the result?
Hi , thanks for reaching out.
For us to reproduce your issue, would you mind sharing the specific supabase action you’re using? Also could you share your whole action configuration if possible?
Hi - it’s simply just a ‘Select Row’ step from the Supabase module
Nothing else on the flow has been set up yet
Thanks for the information. I’ll try to reproduce and get back to you asap
Hi , I couldn’t seems to reproduce your issue on my side, as I executed the workflow normally. The different I observed is that I used the workflow v3, would you mind switching to workflow v3 and try again?
can you try reducing the number of rows your Supabase action returns and see if it helps?
/ @U05FUC30Q01 It works with less rows returned - the ‘Results’ tab appears
However, I think there is just simply a bug with Pipedream displaying the data
When I run the workflow (not just a test) without such a restriction, e.g. back to my original limit of 100,000, it still does not show the results from Supabase - but it is able to proceed to the next step
• Example attached
You can see it just does not bother showing the Supabase step at all
But I know that the data would be located at:
steps.get_workspace_1_campaign_list.$return_value.data
And therefore was able to use it
So I believe it’s just possibly exceeding the maximum character count able to be shown - so it’s not displaying anything, yet data is still there?
Odd occurrence
FYI this occurs on both v2 and v3 views
Gotcha, thanks for trying that! Yeah this was a recent change we pushed. Some users were having issues loading the UI when the step export data was too large. Workflow execution is not affected, so it would run normally it’s just the UI that doesn’t show
Would it be worthwhile showing some results then? This way we can see a portion of what was returned
And the rest can simply be truncated off
Yes definitely! We actually intended it to show a message alerting that the export was elided. I’m checking with the team
Yep just saw that one! It would be good to have just some example results, that way we can still have examples of what we can route / ‘copy path’ for future steps in the flow
Not sure what the status is, but something has been causing a lot of issues with Supabase. Please see attached image.
My flow has been stuck in a loop for 9,268 seconds - well above the default TIMEOUT
This might be important to look into / @U03CXTHK4RF
I have tried turning the flow off, but I cannot stop it from executing?..
Even though it has the ‘paused’ symbol on the Live Monitoring pane
Is there no way to stop something from executing at all in Inspect mode?
Hi , we’ve acknowledged your issue and will take a look as soon as possible
Thanks
Hey , we’re investigating what is happening in your workflow