Delay action: Base delay on date field in trigger using custom field: does not delay for anon user, due to permissions

When using Delay action: Base delay on date field in trigger, using a custom date field: if the rule fires for an anon user then no delay occurs. This is due to permissions being checked in the API v4 call when getting the custom date field value. I think it's OK not to check permissions in this specific API call; this resolves the problem. MR provided.

Issue was observed & fixed on:
CiviRules 3.12
CiviCRM 5.70.2

Edited Oct 11, 2024 by davej

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information