Adding users to groups shouldn't trigger synchronizing the user properties from Azure AD UNDER REVIEW

1

Something interestingly happened.

I wanted to create a few hundred BPS groups to test something unrelated to this topic.

I already had a process for creating the groups and assigning the users. I wanted to utilize it by creating another process with an item list, populate this via excel, and start the first for each row.
So far so easy I had in mind. I got distracted and forgot to add a loop to prevent that all item list rows are processed at ones.
The action for creating the sub workflows was on the path when a new workflow instance is created.
Obviously the execution failed due to the timeout issue, but while writing this post more and more BPS groups are popping up in Portal.

So, while the workflow instance used for importing the data wasn't saved, and the subworkflows haven't been created the BPS groups are being created.
The archive -/db/6/app/26/explore/all - does not contain any new workflows.

Digging deeper:

The parent workflow was executed at 15:29 UTC (17:29) (1)

I joined the LOG_WFDID column with the WFElements table. While the LOG_WFDID column has a value the WFD_ID column is null and new log entries are created for "new workflow" at this moment. (2)

This is really strange. :)

Now it is even more interesting.
It seems, that the transaction was still running and that's the reason why I didn't see the workflow instances. Neither in the Portal nor in SQL Server Management studio. I didn't think of making a dirty read.

I checked this morning and now they show up. It just took about 7 hours to complete everything.

I have now idea how this may have been implemented but they have me respect that this worked out fine. :)

Hi Daniel,

thanks for the suggestion and sharing of all of your findings related to the case. We've already forwarded them to our devs for analysis.