We're seeing some processes start and NOT call the ApplicationProfileSetup activity in our application. I was wondering if anyone could point me to the magic processes that decide after login (for example) to "start an application thread" moving forward as I'd like to see if I can add some debugging to it and find out what and where it's failing.
***Edited by Moderator Marissa to update Platform Capability tags****
Is there anyone on the internal team(s) that can clarify how the handoff occurs post-login? Once the user has been authenticated and run through the custom/non-custom authentication activity, how does the system then decide to start application thread(s) and call the ApplicationProfileSetup data transform?