Issue Summary

In Assets Automation, when configuring a Scheduled rule that must “Run as” a specific user (Executing User), the Automation rule editor UI intermittently shows a spinner / appears to have no user selected for the "Triggered rule will run as" field after saving and reopening the rule.

Despite the misleading UI:

• The rule can still be saved without the expected validation banner that should block saving when no Executing User is set.
• The database record (AO_8542F1_IFJ_ATM_RULE.ACTOR_USER_KEY) correctly contains the Executing User’s user key.

This is therefore a UI-only bug in the rule editor that does not affect rule execution behavior in observed tests, but can mislead admins into thinking no Executing User is set.

Video Demonstration:

Demo-bug.mov

Steps to Reproduce

1. In an instance with Assets / Assets Automation 11.3.1+, go to Automation for Assets.
2. Create a new Scheduled Assets Automation rule.
3. Configure the WHEN condition using an AQL like:
   • Label is not empty
4. Configure any THEN action, for example:
   • Set attribute value – set Label to ${Label} (adds a “” to the Label on every run)
5. Because this is a Scheduled trigger, set a specific Executing User (e.g. an admin). Note that the UI displays a validation banner and does not allow saving while “Run as logged in user” is selected.
6. Save the rule.
7. Observe the rule details screen: the UI shows a spinner in the Executing User field, giving the impression the user is still loading or unset.
8. Navigate back to edit the rule.
   1. Observe that:
      • The Executing User field appears empty / still shows the spinner.
      • There is no validation banner preventing saving the rule, even though the field looks empty.

Expected Results

• The Executing User field in the Automation rule editor should:
  • Display the configured Executing User correctly after saving and re-opening the rule.
  • Show a validation banner and prevent saving if no Executing User is set for Scheduled triggers.
• The UI state (displayed user, spinner, and validation) should be consistent with the underlying configuration in AO_8542F1_IFJ_ATM_RULE.ACTOR_USER_KEY.

Actual Results

• After saving the rule with a valid Executing User and re-opening the rule:
  • The Executing User field shows a spinner and/or appears empty, as in the demonstration video.
  • The rule can still be saved without the expected validation banner, even though the field looks empty.
• The database shows that the rule does have a valid Executing User:
  • AO_8542F1_IFJ_ATM_RULE.ACTOR_USER_KEY contains the correct user key.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available