Recently, about a few months ago, SailPoint made a change to not allow saving of changes to Identity Profile mapping configuration when there are Identity Tasks running. You get a popup error saying: The system cannot “Update Identity Profile” while Identity Tasks are in progress."
This is particularly annoying because there are times I have to wait for hours before I can make a change. And to not lose the changes I made — especially when there are substantial changes – I need to keep another window to make sure I don’t get kicked out of my session otherwise I lose the changes I had made.
This is truly an impediment to development and I’d like to know if anybody else is experiencing grief over this?
I have created an idea — to be honest I think this is a bug that needs to be addressed, anyway here’s a link to the idea in case folks would like to upvote: https://ideas.sailpoint.com/ideas/GOV-I-3892
SailPoint has marked the idea as Future Consideration but hopefully if more folks ask for it, they may work on it sooner. Thanks!
Please be sure you’ve read the docs and API specs before asking for help. Also, please be sure you’ve searched the forum for your answer before you create a new topic.
Please consider addressing the following when creating your topic:
What have you tried?
What errors did you face (share screenshots)?
Share the details of your efforts (code / search query, workflow json etc.)?
What is the result you are getting and what were you expecting?
This also prevents a spiral of changes from processing because it can no longer be stopped since you cannot make any changes until all processing is done. This means that if you accidentally saved some changes that you do not want processed, you just need to let it all get processed through before you can make any new changes to correct it. Which could be catastrophic if they are related to CloudLifecycleState changes that could cascade down to permissions for roles, entitlements and access profiles or even workflows that is triggered off by such attributes.
Thanks for the idea @rtatco. Fed up with the tasks running which are taking more hours to complete. This is stopping identity processing as well. Recently we have waited for more than 8 hours to process set of identities manually.
It should be in such a way that the tasks should not be a roadblock for other activities, or the tasks should get completed within 30mins.
“Waiting for the washing machine to be available at the laundromat” means standing by at a laundromat, observing the washing machines until one becomes free so you can load your clothes to start a wash cycle.
Key points about this situation:
First come, first served:
At a laundromat, the first person to reach an available washing machine gets to use it.
Monitoring the machines:
You need to watch the machines to see when a cycle ends and the door opens, indicating it’s ready for a new load.
Potential waiting time:
Depending on how busy the laundromat is, you might need to wait a few minutes for a machine to become free.
What you can do while waiting:
Sort your laundry:
Prepare your clothes by sorting them into appropriate wash cycles before a machine opens up.
Check for change:
Make sure you have enough coins or a payment method accepted by the laundromat to pay for the wash cycle.
Be patient:
Avoid trying to “reserve” a machine by leaving your clothes on top of it while you’re away.
This is how bored I got while waiting to be able to save my changes. It has been longer than 2 hours. Do I kill the aggregation task that is running? Do I turn off the aggregation schedule altogether?
I understand laundromat etiquette. Do I just take out someone else’s clothes? I can’t even do that! This is truly unacceptable. SMH. Sigh. Every single time we need to make changes my fear is: Is the washing machine gonna be taken? I need to make my changes as quick as possible before it does. Crap, it it started running while I was making my changes.
The screenshot is what it shows how many more is there to do after 2 hours of wait. It started with 100K+, this is agony.
Please be sure you’ve read the docs and API specs before asking for help. Also, please be sure you’ve searched the forum for your answer before you create a new topic.
