Anyone experience this? I am wondering does this only happens to my tenant (or maybe the Singapore region only) or it actually happened to some other fellow community members here before?
Today, I am working on my own automation by using the various APIs, part of my automation involve the creation of policy-boundary.
After creating a few boundary using API (and bind them to newly-created user group created by API as well), I delete the boundary in the UI.
And sure enough it says I can't do that because some user group is still referencing it.
So, I deleted the user group in the UI.
Afterwards, when I try to delete the boundaries again in UI, it failed and return me the error message that reads something like "it is still reference by policy with the id xxxxxxxx and the usergroup yyyyy".
Now, when I use API-swagger to query the list of policy and list of usergroup, I just don't see xxxxx and yyyyy!
So this means not just the UI is not reflecting the true status of what's happening inside Grail, but even the API also not reflecting!
Spent hours trying whatever I could think of, but no answer.
Eventually give up and thinking to myself: "Must be the Grail hasn't update yet"
And after around 2 or 3 hours, come back and try again, now it can be deleted.
Actually, the reason that leads me to suspect it is the backend that got delayed, is because I experiencing something similar few days before.
What happened few days ago: I created application successfully via API (hence, returned me the Application ID), but when I try to assign an application-detection-rule to the newly created Application, it just returned various kind of errors indicating that the ApplicationID couldn't be found, no matter what I try.
Eventually how I successfully resolved it, is by just putting a line 'sleep 10' in my automation-script, essentially asking it to wait 10 seconds between application-created and creating-application-detection-rule, then everything works smoothly.
What happened few days ago, is a delay of like 10 seconds or so, that's why I thought might be my internet slow or the API is protecting itself by starting to throttling (because who knows, maybe I calling it too frequent)
But then, what happens today with the policy, boundary, and user group needs me wait hours (not even minutes). So I thought I should actually share this here today.
These 2 'incidents' are easily causing me few hours of time wasted in the past few days......
