I’ve updated my project since it is now in a team workspace.
(The doc didn’t say it but I figured I must now set a project_id)
Still, I trigger the workflow with an API call but it’s not able to find the document I previously set.
So either I’m not sending the document to the right place (I’m including the workspace ID), or something else…
I don’t understand what’s wrong and this is a flow I use daily in prod… so pretty urgent. I can share my code privately. But note that it worked fine until I switched from “use personal workspace” to “use workspace” and I changed the bearer ID + added project_ID.
files are sent with a 200 return previously to running the pipeline.
Hey @Edouard_r! 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 @Edouard_r – The likely issue is that files are stored in separate directories for personal (user_id/) vs. team (project_id/) workspaces. When you switched to a team workspace, your pipelines started looking for files in the project_id/ directory, but your old files are still in the user_id/ directory.
Could you please re-upload your files using your workspace API key (note that this is different from your personal API key) and the correct project_id. Then run your pipeline with the same workspace credentials and project_id.
