Is it possible that this “stage_ row” was somehow inserted into the job after ingest via a bug? The sheet produced by the “view ingested sheet” feature doesn’t not have this row in it, despite it being there now. As Toni mentioned it would be near impossible for the user to accidently copy this in to the job via the UI when it is from a previously ingested sheet.. Are there any bugs or mechanisms where this could happen?
Given the occurrences of the server crashing and apparent strange functionality, maybe it is a good idea to have some tracking of changes occurring through the UI to investigate these. If the audit table could have some kind of information on the mechanisms of change (eg. insert row, copy-paste row, find and replace) that would be good information to have.
Toni report strange behavior in UI, however it is very hard to reproduce it, an audit table of the staged_row can help to trouble shoot issue.
=========================================================
Is it possible that this “stage_ row” was somehow inserted into the job after ingest via a bug? The sheet produced by the “view ingested sheet” feature doesn’t not have this row in it, despite it being there now. As Toni mentioned it would be near impossible for the user to accidently copy this in to the job via the UI when it is from a previously ingested sheet.. Are there any bugs or mechanisms where this could happen?
Given the occurrences of the server crashing and apparent strange functionality, maybe it is a good idea to have some tracking of changes occurring through the UI to investigate these. If the audit table could have some kind of information on the mechanisms of change (eg. insert row, copy-paste row, find and replace) that would be good information to have.
Cheers,
Lizzi