Describe the problem/error/question
I have a Google Sheet containing thousands of rows and a dozen columns of data.
My goal is to parse specific columns through a series of checks. If any check results in an error, I want to log certain data from the original sheet into a separate log (also a Google Sheet), including the error message, and then proceed to the next row in the original list. If the parsing process completes without errors, the output should be written to the log sheet, but instead of an error, it will contain the desired processed data.
Am I overcomplicating this?
Previously, when encountering an error, I would add a node to isolate the problematic item, log it, and then loop back to the next item.
I had to omit a dozen error logging steps to keep this post concise, but they followed the same pattern: pausing, logging to the sheet, and then returning to the loop.
What is the error message (if any)?
For my last Google Sheet save operation, I sometimes receive the error "cannot determine which item to use" for the fields. This error is intermittent. My suspicion is that the logging and looping back might be causing the issue, as the process stops on errors without the return loop.
To clarify:
When an error occurs, all data is written correctly (except for the AI-generated portion).
When there are no errors (up until the final spreadsheet write at the end of the loop), it misses all original fields not related to the AI processing. It seems to lose track of the source row and doesn't return all the expected column data.
Please share your workflow
Share the output returned by the last node
Information on your callin.io setup
- callin.io version:1.98.2
- Database (default: SQLite):default
- callin.io EXECUTIONS_PROCESS setting (default: own, main):default
- Running callin.io via (Docker, npm, callin.io cloud, desktop app): docker
- Operating system:Ubuntu via Docker
I'm uncertain if the issue lies with the workflow or if there's a typo.
You're referencing the Edit Fields
node, but no node with that exact name exists. The closest match appears to be the Edit Fields1
node.
This difference could be significant.
Perhaps try renaming the Edit Fields1
node to Edit Fields
?
Apologies, that's not quite it. When I tried to condense this to fit the page, I inadvertently removed a significant portion, then added it back, and the '1' was included at that time.
I was able to convert a part of this into a subflow using the new 'right-click → create subflow' option, which now allows me to demonstrate my error logging setup.
This modification actually appears to have resolved the issue. The workflow still follows the same path, but it now calls a subworkflow for the AI-related tasks. My hypothesis is that the workflow was too lengthy, potentially causing a memory issue?
This discussion was automatically closed 7 days following the last response. New replies are no longer permitted.