The Assets default Object custom field and the Assets Read Only customfield, both have a Filter Assign Scope - to Auto populate the field on the Issue created event, and (optionally for the former) on the Issue updated event.

The filter Assign scope may be set with dependency on another Assets field (using a placeholder), which in turn may also have a dependency on another custom field.

The filter Assign scope of the last custom field in the chain (in this example) may not populate when an issue is created/updated, due to a race condition: the custom field its dependent upon was not yet populated.

This can be resolved by triggering an Issue Updated event right after the creation, however - as a User it will be more beneficial for me to add a short delay (in ms) to the filter assign scope, so it may execute a few ms after its trigger:
The User will manually select a Host object when creating a ticket / issue in cf_1

cf_2 will be populating with the OS of the host selected, with a filter assign scope: object HAVING inR(Key = ${cf_1})

cf_3 will be populating with the OS_License of the OS object in cf_2, with a filter assign scope: object HAVING outR(Key = ${cf_2})

The expected result on issue creation - all 3 custom fields are populated.

Actual result - only cf_1 and cf_2 are populated, cf_3 has no value since both cf_2 and cf_3 Filter Assign scope execution occurred approximately at the same time...

If cf_3 had a 50ms delay it would have been populating....