-
Notifications
You must be signed in to change notification settings - Fork 9.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test workflow bug... #12396
Comments
Hey @BandicootApps, We have created an internal ticket to look into this which we will be tracking as "N8N-8022" |
Hey @BandicootApps Can you be more specific and provide an example workflow showing what isn't working so we can reproduce it? |
Hi Jon,
Many of my workflows involve pulling from a Google Drive folder. I then do
a little bit of manipulation those files and upload them to my Supabase
database. The issue I’m encountering seems to occur (or atleast i think
occurs) when I duplicate a workflow and change the settings. Despite
updating the google drive node settings and/or IDs in the duplicated
workflow, it sometimes pulls data from the wrong Google Drive file, as if
it’s still referencing the original workflow’s configuration. But it also
doesn't stop there once this has happened it seems to do it across all my
workflows once it has happened in one.
I suspect the duplication process might be causing the issue because I’ve
noticed this problem occurs more frequently after duplicating a workflow.
However, it’s not limited to those cases—it has happened in other instances
too.
Previously, I reported a similar issue, and the response suggested this
might only affect the testing environment, with the production version
running as expected. While I’ve been able to work around this limitation,
I’ve recently encountered the same problem during the building and testing
phase of a workflow. This prevents me from properly testing the flow with
the correct data. Even when I’m confident I’ve set the correct variables,
the production version encounters errors. Unfortunately, I can’t diagnose
these errors properly because the test environment is pulling entirely
different data.
…On Mon, 30 Dec 2024 at 19:25, Jon ***@***.***> wrote:
Hey @BandicootApps <https://github.com/BandicootApps>
Can you be more specific and provide an example workflow showing what
isn't working so we can reproduce it?
—
Reply to this email directly, view it on GitHub
<#12396 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/BHW3YTH4V6JGANEONHE6VE32ID7RJAVCNFSM6AAAAABULVCLJWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRVGE3DGOJXGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Hey @BandicootApps, Do you any specific examples or screenshots of the duplicated workflows causing issues? It would be handy to know which fields you are using as an example if it is a field that is dynamic and you don't refresh the list after duplicating something it will cache the previous value but in the UI you should also see the older name of the file. It would be great if you could break down the issues so we can see exactly what is happening with Supabase and exactly what is happening with Google Drive so we don't get things mixed up. The original issue with Google Drive and the Trigger I am aware of and we have the dev ticket opened to resolve that so I think we can skip that node for now and focus this post on the other nodes. If you have specific workflow examples and a video showing the issue as well that could help. |
Bug Description
I previously reported an issue where testing a workflow pulls incorrect data. You advised me to check if the workflow works properly when activated and running in production. At the time, it did work in production, so I let it go.
Now the issue has returned. When I test my workflow, it processes incorrect data successfully, even though the data is wrong. However, the production (active) version of the workflow is now throwing errors. This makes it impossible for me to properly test and resolve the issue.
To add to my frustration, the last time I raised this, it felt like the problem wasn’t going to be addressed because it worked in production. Unfortunately, this is now a recurring issue that has wasted a lot of my time.
Please prioritize fixing this bug. If it isn’t resolved soon, I’ll have to consider moving away from n8n.
To Reproduce
...
Expected behavior
for it to actually work...
Operating System
mac
n8n Version
[email protected]
Node.js Version
i am using online
Database
SQLite (default)
Execution mode
main (default)
The text was updated successfully, but these errors were encountered: