Managed configuration not getting pushed onto some devices in work profile

Same on our side with the AMAPI, for both work profile and fully managed devices. I created a ticket for this a couple of weeks ago. According to the support, the Engineering team is working on it. Let's hope it's getting fixed soon.

Thanks so much for highlight this @Florian, I've found the ticket.

@Prathik  I've added a note to that existing ticket to say you are also experiencing this. It's likely we might need more information to reproduce, so if that's so I'll come back. 

Thanks again. Speak soon.

Lizzie

Hey @Florian and @Prathik,

Did this resolve itself in the end? 

Thank you,

Lizzie

@Florian@LizzieHas this issue been rolled out across the board?
We are suddenly, as of a week or two ago, and right now, experiencing this exact issue.

Our companion app, set to required for install and setup_action, is stuck on continuing its setup process due to managed configurations not arriving.
We use managedconfiguration rather than managedconfigurationtemplate for this particular app, as its part of every policy a device receives and is our companion app.

We have noticed, that in some cases, the same device will continuously fail to receive the managed configuration even after multiple factory resets. 
The only way we have been able to force a device through the process, is to patch its policy with one that does not contain the managed configuration, then patch it again with the managed configuration and this then forces through the managed configuration and the app continues its process as normal.

Happy to raise a ticket, but before i do i just wanted to check what the status was of the fix.

Hey @Prathik and @Robert,

Just a quick update to say I have asked for an update on the open ticket regarding the fix rollout. Once there is more of an update I'll relay this back (or perhaps you would be happy to @Florian as you have been fantastic at updating us here - thank you). 

Thanks so much,

Lizzie