In the automation logs it shows that the 1 record is collected, which I verify again in script console.log, but in the Update all collected record, it fails due to no records in the collection
I’ve done similar automations in a lot of places without issue, only here I stumble upon this behavior.
In the community post I’ve referenced the solution was doing manual runs instead of simulated ones,
I work with manual and triggered runs here.
What I’ve tried so far:
duplicating the automation
turning the search and update into code and use a custom defined variable as the collection
using a static record ID as the search value
All with the same result of the automation failing.
I hope I’ve covered the important details if further information is needed I will update this ticket and hopefully the issue will be found an solved.
I’m greatfull if any of you maybe have an idea what the issue could be if it should be an user error
Thanks for your help on this one @Tim , for taking the time to dig into the issue and point me in the right direction!
What was going wrong?
The problem seemed pretty confusing at first: the automation correctly found the record (confirmed by the logs and a console.log check), but then failed at the “Update all collected records” step — claiming there were no records to update.
I’ve used this pattern in other automations without any issues, so this behavior stood out as unusual.
What caused it?
Tim spotted the actual issue (thanks again!):
It wasn’t the search step that failed — it was the update action throwing an error silently because of a long string being written into a multi-text field.
The server didn’t like the string size, but instead of returning a helpful error, it made it look like the record collection was empty. This is definitely something to improve in the log output going forward.
How to move forward
Try reducing the length of the string you’re writing into that multi-text field — this should unblock the automation.
As a helpful debugging tip: you can enable “Continue on Error” in the action settings. That way, even if something fails, you’ll still get access to the Most Recent Error variable, which can make troubleshooting a lot easier.