when I load my interface in a separate tab to test the workflow, I get this error in the console:
Error in trigger initialization process: Error: Supabase URL and key must be provided either through config or environment variables
at R3 (_app-82817052769b5663.js:3371:95516)
at R4 (_app-82817052769b5663.js:3371:95770)
at F3 (_app-82817052769b5663.js:3379:141385)
at _app-82817052769b5663.js:3399:6362
at _app-82817052769b5663.js:3399:6581
at uU (framework-314c182fa7e2bf37.js:9:84108)
at oV (framework-314c182fa7e2bf37.js:9:113154)
at framework-314c182fa7e2bf37.js:9:111540
at oU (framework-314c182fa7e2bf37.js:9:111606)
at oP (framework-314c182fa7e2bf37.js:9:96235)
api.gumloop.com/form_start_pipeline:1 Failed to load resource: the server responded with a status of 403 ()
I have no supabase node so I think the error refers to the database behind the interface which I have no access to. Also, I don’t understand why it works sometimes after clearing the files uploaded but then crashes again after I’ve ran the workflow once with a file. My workbook link is here: Gumloop | Automation Builder
Hey @innovation-tools! 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.
FYI, it also keeps giving me this error! I really hope i can get some help on this as I’m not sure what I am doing wrong I have tried remaking the flow from scratch too but I always end up running into this error
Hey @innovation-tools, thanks for sharing the detailed info, really helpful. I’ve opened a ticket for this issue so the team can work on a fix. I’ll let you know once it’s resolved.
The issue seems limited to your view; when the interface link is shared with others, the error doesn’t occur. We appreciate your patience while we get this fixed!