Push based, COND_InitialOnly property can fail to be replicated when actor becomes relevant again

COND_InitialOnly properties can be resent when an actor becomes relevant to a client again. However, if the property is push based and it was never replicated the first time the actor was created on the client, the initial only property will not be replicated when the actor becomes relevant again, even if the value has changed.
If the property is not using push model or if it does get replicated the first time, then the property's latest value will be replicated as expected when the actor becomes relevant again.

Create a replicated actor with a push based, COND_InitialOnly replicated property.
When the actor is first spawned on the server, don't change this property from the default value.
After the initial replication, change the property (marking it as dirty) and have the actor become irrelevant to the client.
Once the actor has been destroyed on the client, have the actor become relevant again.

Expected: the actor will be recreated on the client, with the initial only property having the updated value from the server
Actual: the actor will be recreated on the client, but the property will still have the default value

See linked UDN for more info.

I am not able to find world outliner how to enable it?

How to achieve HLSL Multiple Render Target in Material blueprints?

Delay nodes occasionally don't fire the "Completed" output in a nativized build

I'm working on a VR Project and I cannot add Nav Mesh to the stairs??

How can i modify the param name in EQS node

What controls of umg have mouse wheel events in UE4.27?

Bonjour j'ai un petit problème c'est que je ne vois plus l'onglet "scability" pour changer les graphismes de uefn et j'ai pas trouvé l'option pour le faire revenir ?

How does TextureRenderTarget2D get TArray<uint8> type data?

Undefined sysmbol: typeinfo for AActor when cross-compile linux dedicated server on windows

Custom Depth issue fix target