Perfect Test Environment - Flawed in Production

Questions
,
1

I simply need to extract 3 columns of data from a CSV containing multiple columns (say 12) in a specific order - clean up the data format - and then write to a new sheet.

I have a flow:
Start: n8n form submission (to upload csv)
→ extract from csv
→ edit field (to set 3 columns to extract)
→ Google Sheet (to append data)
→ Code (to cleanup trailing apostrophes)
→ convert to file
→ Send Gmail (with CSV attached).

Credentials required for Sheets and Email or set correctly. The flow executes perfectly. The only changes made to SWITCH test environment to production, is to ACTIVATE flow and to use the PRODUCTION URL in the n8n form.

Yet the production environment works without error, but outputs an empty file - just the three headers with no content. This does not happen in test, where I get the CSV file in my email perfectly.

There are NO ERROR Messages in either flow.

Information on your n8n setup

instance information

Debug info

core

1.77.3

Source Code
GitHub - n8n-io/n8n: Fair-code workflow automation platform with native AI capabilities. Combine visual building with custom code, self-host or cloud, 400+ integrations.
License

Sustainable Use License + n8n Enterprise License
Instance ID
1194af871ae887fe6358d9a1a8c9b0b90d1d711fa93d2166d28460cb411a9a25

  • n8nVersion: 1.77.3
  • platform: docker (cloud)
  • nodeJsVersion: 20.18.2
  • database: sqlite
  • executionMode: regular
  • concurrency: 5
  • license: community
  • consumerId: 00000000-0000-0000-0000-000000000000

storage

  • success: all
  • error: all
  • progress: false
  • manual: true
  • binaryMode: filesystem

pruning

  • enabled: true
  • maxAge: 168 hours
  • maxCount: 2500 executions

client

  • userAgent: mozilla/5.0 (windows nt 10.0; win64; x64) applewebkit/537.36 (khtml, like gecko) chrome/132.0.0.0 safari/537.36 edg/132.0.0.0
  • isTouchDevice: false

Generated at: 2025-02-11T05:09:28.863Z

2

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
3

Hi @

Weird this is happening indeed. If the only change is enabling the workflow and using the production url things should work.

Can you give it a try on our cloud instance so we can exclude the local setup factor? Does it work on cloud?

Thanks!

4

Hi,

I am on the CLoud Instance (free trial) — is that the reason why it won['t go to production>?

(I copied the details from within the platform — I am not smart enough to self-host)

:slight_smile:
D

5

It shouldn’t be an issue, can you share the entire workflow putting it inside a code block

Like this

(I’m on my phone, have a hard time doing it myself by editing your original post)

1 Like
6

Thanks. (I tried before but it just dumped the json) but now it seems ok?

Cheers

7

ANy ideas about this yet please?

8

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.