Steps to replicate: Start with a new app. Add a second table. For clarity, let's call the tables Invoices and Payments. In the payments table, add an EnumList with a ref base pointing to the invoices table - lets call it [related invoices]. Create an action for the invoices table that updates a field, for example set [status] to "Paid". In the Payments table, make a Yes/No column, let's call it "Mark Paid?". Create a few records in each table and populate the enumlist column you added to the payments table. Now create a bot that is triggered by data change in Payments. Add a step that will activate the Mark Invoice Paid action item, using [related invoices] as the row reference.
Expected Results: When a row in payments has [Mark Paid] set to TRUE, the related invoices have [status] set to paid. Or, when trying to select the action in the bot, the interface explains why this isn't possible.
Actual Results: Bot fails to trigger action item. On testing, an error message mentioning something about "Parent" and "ImagePrevious" is shown.