Internal error: Upstream tool called push record in update mode

[influentiale]

I am trying to use the python tool to manipulate some data then load the resulting data frame to a Teradata table. The flow works locally but when I try to schedule it on server I get the following error “Internal error: Upstream tool called push record in update mode”. I have not been able to find any documentation on this error. 

[danilang]

@influentiale 

Do you have all the required python libraries installed on the server? 

Can you post the entire output log?

Dan

[influentiale]

@danilang Thank you for the response, and thank you for your patience as I am very new to testing out Alteryx. 

As for the libraries being installed on the server, I doubt it since it is a corporate instance, unless having the "Package.installPackages("package_name") does the trick. The validation step completes successfully when I try to schedule the job to server if I do not have the load portion enabled that is to push it to Teradata, the two python steps complete successfully. It is when I enable that last load function that I get the Internal error. Below is what I see log wise.

Message Type	Process or Tool Id	Details
Information
-1	Running at a Low Priority.
Information
1	Requirement already satisfied: emspy in c:\windows\system32\config\systemprofile\appdata\roaming\python\python36\site-packages (0.4.1)
Information
1	Requirement already satisfied: numpy>=1.13.3 in e:\program files\alteryx\bin\miniconda3\envs\jupytertool_venv\lib\site-packages (from emspy) (1.16.4)
Information
1	Requirement already satisfied: pandas in e:\program files\alteryx\bin\miniconda3\envs\jupytertool_venv\lib\site-packages (from emspy) (0.24.2)
Information
1	Requirement already satisfied: networkx in c:\windows\system32\config\systemprofile\appdata\roaming\python\python36\site-packages (from emspy) (2.5)
Information
1	Requirement already satisfied: future in c:\windows\system32\config\systemprofile\appdata\roaming\python\python36\site-packages (from emspy) (0.18.2)
Information
1	Requirement already satisfied: python-dateutil>=2.5.0 in e:\program files\alteryx\bin\miniconda3\envs\jupytertool_venv\lib\site-packages (from pandas->emspy) (2.8.0)
Information
1	Requirement already satisfied: pytz>=2011k in e:\program files\alteryx\bin\miniconda3\envs\jupytertool_venv\lib\site-packages (from pandas->emspy) (2019.1)
Information
1	Requirement already satisfied: decorator>=4.3.0 in e:\program files\alteryx\bin\miniconda3\envs\jupytertool_venv\lib\site-packages (from networkx->emspy) (4.4.0)
Information
1	Requirement already satisfied: six>=1.5 in e:\program files\alteryx\bin\miniconda3\envs\jupytertool_venv\lib\site-packages (from python-dateutil>=2.5.0->pandas->emspy) (1.12.0)
Information
1	On <root>(root)...
Information
1	=== Starting to update subtree from 'FDW (database_group)' ===
Information
1	On FDW(database_group)...
Information
1	-- Added 3 databases
Information
1	On Dimensions(database_group)...
Information
1	-- Added 20 databases
Information
1	On APM Events(database_group)...
Information
1	=== Starting to update subtree from 'Validated Profiles (database_group)' ===
Information
1	On Validated Profiles(database_group)...
Information
1	On P9: Validated Event Set ALL FLEETS Events(database_group)...
Information
1	-- Added 66 databases
Information
1	On P10: FSI Events - DO NOT DELETE Events(database_group)...
Information
1	-- Added 21 databases
Information
1	On P9: Validated Event Set ALL FLEETS Events - All Events(database)...
Information
1	Using database 'P9: Validated Event Set ALL FLEETS Events - All Events'.
Information
1	On Download Information(field_group)...
Information
1	-- Added 21 fields
Information
1	On Processing(field_group)...
Information
1	-- Added 2 fields
Information
1	=== Starting to update subtree from 'Download Sync (field_group)' ===
Information
1	On Download Sync(field_group)...
Information
1	-- Added 9 fields
Information
1	On Flight Information(field_group)...
Information
1	-- Added 9 fields
Information
1	On Processing(field_group)...
Information
1	-- Added 3 fields
Information
1	=== Starting to update subtree from 'Fleet Group (field_group)' ===
Information
1	On Fleet Group(field_group)...
Information
1	-- Added 9 fields
Information
1	On Aircraft Information(field_group)...
Information
1	-- Added 20 fields
Information
1	On Fleet Information(field_group)...
Information
1	=== Starting to update subtree from 'Physical Data Configuration Info (field_group)' ===
Information
1	On Physical Data Configuration Info(field_group)...
Information
1	-- Added 5 fields
Information
1	On Navigation Information(field_group)...
Information
1	-- Added 3 fields
Information
1	On Takeoff(field_group)...
Information
1	=== Starting to update subtree from 'Runway (field_group)' ===
Information
1	On Runway(field_group)...
Information
1	On ID(field_group)...
Information
1	-- Added 4 fields
Information
1	On Geometry(field_group)...
Information
1	-- Added 12 fields
Information
1	On ILS(field_group)...
Information
1	-- Added 9 fields
Information
1	On Navigation Information(field_group)...
Information
1	-- Added 3 fields
Information
1	On Landing(field_group)...
Information
1	=== Starting to update subtree from 'Runway (field_group)' ===
Information
1	On Runway(field_group)...
Information
1	On ID(field_group)...
Information
1	-- Added 4 fields
Information
1	On Geometry(field_group)...
Information
1	-- Added 18 fields
Information
1	On ILS(field_group)...
Information
1	-- Added 25 fields
Information
1	On Flight Review(field_group)...
Information
1	=== Starting to update subtree from 'Data Quality (field_group)' ===
Information
1	On Data Quality(field_group)...
Information
1	-- Added 5 fields
Information
1	On Flight Review(field_group)...
Information
1	=== Starting to update subtree from 'Duplicate Detection (field_group)' ===
Information
1	On Duplicate Detection(field_group)...
Information
1	-- Added 7 fields
Information
1	On Ordering(field_group)...
Information
1	-- Added 1 field
Information
1	=== Starting to update subtree from 'Data Information (field_group)' ===
Information
1	On Data Information(field_group)...
Information
1	-- Added 12 fields
Information
1	On Profiles(field_group)...
Information
1	On Validated Profiles(field_group)...
Information
1	On P9: Validated Event Set ALL FLEETS(field_group)...
Information
1	=== Starting to update subtree from 'Processing Status (field_group)' ===
Information
1	On Processing Status(field_group)...
Information
1	-- Added 12 fields
Information
1	On Post-Processing(field_group)...
Information
1	-- Added 117 fields
Information
1	=== Starting to update subtree from 'Profile 9: Event Information (field_group)' ===
Information
1	On Profile 9: Event Information(field_group)...
Information
1	-- Added 7 fields
Information
1	Fleet: Getting key-value mappings from API. (Caution: Some fields take a very long time)
Information
1	Data Quality (master): Getting key-value mappings from API. (Caution: Some fields take a very long time)
Information
1	Duplicate Detection (Master): Getting key-value mappings from API. (Caution: Some fields take a very long time)
Information
1	Flight Classification: Getting key-value mappings from API. (Caution: Some fields take a very long time)
Information
1	P9: Processing State: Getting key-value mappings from API. (Caution: Some fields take a very long time)
Information
1	P9: Status: Getting key-value mappings from API. (Caution: Some fields take a very long time)
Information
1	Sending and opening an async-query to EMS ... Done.
Information
1	=== Async call: 1 ===
Information
1	Raw JSON output to Pandas dataframe...
Information
1	Airframe: Getting key-value mappings from API. (Caution: Some fields take a very long time)
Information
1	Takeoff Runway ID: Getting key-value mappings from API. (Caution: Some fields take a very long time)
Information
1	Landing Runway ID: Getting key-value mappings from API. (Caution: Some fields take a very long time)
Information
1	P9: Event Type: Getting key-value mappings from API. (Caution: Some fields take a very long time)
Information
1	P9: Severity: Getting key-value mappings from API. (Caution: Some fields take a very long time)
Information
1	Done.
Information
1	Received up to 25000 rows.
Information
1	=== Async call: 2 ===
Information
1	Raw JSON output to Pandas dataframe...
Information
1	Done.
Information
1	Received up to 50000 rows.
Information
1	=== Async call: 3 ===
Information
1	Raw JSON output to Pandas dataframe...
Information
1	Done.
Information
1	Received up to 73584 rows.
Information
1	Done.
Information
1	SUCCESS: writing outgoing connection data 1
Information
2	Requirement already satisfied: PyYaml in e:\program files\alteryx\bin\miniconda3\envs\jupytertool_venv\lib\site-packages (5.3.1)
Information
2	SUCCESS: reading input data "#1"
Information
2	SUCCESS: writing outgoing connection data 1
Error
4	Internal error: Upstream tool called push record in update mode

[fed_]

Hi @influentiale I'm facing the same issue: where you able to fix it? Would you mind sharing the solution?
THanks!

[abhishekAlteryx]

Hi @fed_ , were you able to fix this issue? I have tried a bunch of different hacks, but nothing works.

Thanks!

[fed_]

@abhishekAlteryx no, unfortunately no luck for me either... 

[walterosborne]

Hi @abhishekAlteryx, same question to you - any solutions?