The issue is seen when bringing up a spoke using a new hub (with a newly created hub profile). The peer paths are not being created when an overlay endpoint is configured on a spoke WAN interface, along with an overlay traffic steering path and application policy statement. 

Overlay is not establishing

Configs were successfully applied to the devices.

Check the name of the hub. If the hub name has spaces in it, that can cause this behavior. Clone the hub profile and rename it with underscores.

Spaces are not allowed as defined here: https://www.juniper.net/documentation/us/en/software/mist/mist-wan/topics/topic-map/hub-profile.html step #3.

"The name must be 2-32 characters long. It can contain only letters, numbers, and underscores."