
lsr4m (lsr4m) asked a question.
Hi,
I've created a manager linked object (primary and associated) in okta user schema, however when i try to use "Set Linked Object Value for Primary" card in okta workflow, i get an error "Failed to load" in primary name. I assume when the schema is already defined, i should be able to fetch this. What am i missing here?
P.S. - I've tested the API in postman and works fine.
Thanks,
Shivam

@lsr4m (lsr4m) - The "Failed to Load" often indicates a timeout occurred when attempting to dynamically load the list of possible values. If you have too many linked objects defined it is possible the enumeration process is exceeding the time limit and resulting in Failed to Load. You can review the query duration using Chrome Dev Tools (by collecting a HAR). If the "time" of the request exceeds 60 seconds then this condition is definitely met.
Sometimes a card is malfunctioning and the failed to load is instant. I've created 3 linked objects, Added some values to some users for one of them. I then added the card in Workflows, and it dynamically loads them for me successfully.
If this turns out to be a timeout because you are extensively using these linked objects you are likely going to need to leverage Custom API Action (CAPIA) to perform the action.
We only have one linked object in our tenant. I suppose this could be card malfunction as i receive the "unable to load" error within a second. I'll raise a support tick for it. Thanks Tim.
Hi there,
Was support able to help out here Shivam Mukhi? We are also running into this issue trying to automate manager linked object assignment to the direct report.
https://support.okta.com/help/s/question/0D54z00009ZzfT1CAJ/set-linked-object-value-is-unable-to-load-primary-name?language=en_US Fixes this issue.
I think you meant this link. At least that's what fixed it for me!
https://support.okta.com/help/s/article/Workflows-Okta-connectors-Linked-Object-actions-returning-a-Failed-to-Load-error-in-dropdown?language=en_US