cancel
Showing results for 
Search instead for 
Did you mean: 

IPS job is taking too long

Dagmar
Explorer
0 Kudos
779

Dear all,

we have around 52 000 users in the System /Succesfactors. (Source system)

We have IAS in place and Embedded Analytics (Both: Targets)

and usually the read job in the IPS is taking 5-6 hours to sync the users from the successfactors to both target systems!

When I ran the re-sync, the job stopped after 5-6 days, processed only 32 000 users,

this is nightmare.

Does anyone have a similar experience and the solution please?

Thank you!

best Regards,

Dagmar

View Entire Topic
Colt
Active Contributor

Yes Dagmar,

yes, it's a nightmare, I agree. We faced the same issue (~ 60k users) and runtimes of 3-4 days when resyncing. This only worked if you were lucky. You won't be able to change the slow SFSF API. In your scenario you may only declare a few attributes using expand e.g. personKeyNav,personKeyNav/userAccountNav

Initially, we turned to sf.page.size, but a value of 1000 led to longer runtimes. It's better to leave 100 here. The most important property for you could be ips.timeout.read with a value of 360000 (that's seconds). Helped us, you don't need the resync that often, usually after adjusting a transformation. If it ran, then the READ jobs will do.

Hope that helps 🙂

Cheers Carsten

Dagmar
Explorer
0 Kudos
thank you!