Thank you for your reply. That’s a bummer that Airtable won’t accept “empty” or “erase”. I had found this “ifempty-erase” solution in an old Airtable thread (https://community.airtable.com/other-questions-13/is-there-a-way-to-clear-empty-a-field-with-a-zap-update-15963), where it’s written as if it should be able to handle linked records. Is that info incorrect or oudated?
I can see how to employ a 4-way router for the separate cases with “data exists” filters between it and the update module.
If the candidates → Iterator → filter out empty values → Array aggregator → map procedure is better I would appreciate trying to learn it. However, must confess I’m a Make newbie and am somewhat bewildered by the architecture. I have done a fair bit of automations in Airtable and Zapier, but Make feels very different.
The current setup is Airtable search → Iterator → Iterator → Airtable update (-> Skip for error handling). This is due to needing to parse first days, then events for those days (linked records). This I had to ask about in this post ( Airtable update record updates only first item in array in a Bundle ) with the solution with two Iterators after each other was provided. I must admit I don’t exactly understand what the Iterators do.. 
.
I already have the record IDs to update (users to events), but may need to add an extra search step to find out the Airtable user record IDs. I currently work with an abstraction user that I have created separately, to be able to filter out inactive users in different forms and views.
To return to the question of deleting linked records, how does that play out here? If A has been linked before but then gets deleted in the original setting so that it would need to be updated by this scenarion (to unlink the linked record), how would one do that? Isn’t that what ifempty/erase is for?
Cheers,
Björn
PS. I didn’t understand what exactly you meant with a redacted output bundle? From where, all modules, or?