JoseReyes (Customer) to rsaSFDCadmin (RSA): asked a question.
Any downsides to running identity, account and entitlement collections multiple times per day?
I'm currently using web services to trigger identity, account and entitlement
collections throughout the day. I make sure to run any rules that need to be
ran immediately afterwards. I keep seeing the run ID number increase by quite
a bit each day so that makes me wonder, are there any downsides to collecting
data so often?
collections throughout the day. I make sure to run any rules that need to be
ran immediately afterwards. I keep seeing the run ID number increase by quite
a bit each day so that makes me wonder, are there any downsides to collecting
data so often?
collectors multiple times per day. Based on the fact you are using
WebServices to schedule your collections I assume you are not on the current
version of the product and are not leveraging this new feature.
Depending on how old a version you are on there are some known issues with the
scheduler that could cause problems with Rules, Collections and other
scheduled items when **_new_ **items are being added to the scheduler.
Ironically using the WebService to run a collection effectively sets up a
**_new_ **item in the scheduler **_each_ **time you run the collection that is
deleted as soon as it is completed. This is compared to setting the
collection up in the scheduler which creates one item in the scheduler that is
permanent.
Increasing the number of times you add items to the scheduler increases that
chance of a random deadlock that might cause the scheduler to misbehave. Note
that this problem is insidious as the scheduled item that is corrupted is not
the one that is created but an existing item in the schedular at the time the
new items was created.
Again this is resolved in the latest patches for 7.5.2. If you experience
issues with Rules intermittently not running on time you should consider
upgrading to the current version. This fix will not be back ported to
unsupported versions.