Share all details about your problem, including any error messages you may have received.
Hello, SailPoint Developer Community,
We recently had some identities that had their Joiners skip processing with the rapidSetupProcessingState as “skipped”. We’re trying to understand how this “skipped” status is being set so we can determine why these identity cubes did not have their Joiner launch. We are looking for any and all information you might have on the topic to help us understand how “skipped” is set. Thank you!
In Rapid Setup, rapidSetupProcessingState = skipped is typically set when the identity is intentionally excluded from Joiner processing (i.e., it doesn’t qualify to be picked up).
The two most common causes:
“Exclude Uncorrelated Identities” is enabled in Rapid Setup Joiner config → any identity not correlated to an authoritative account gets skipped.
Trigger Filters don’t match (or Joiner isn’t enabled globally / for the authoritative app), so the identity never qualifies to launch Joiner. Rapid Setup Joiner must be enabled globally before it can run per-app.
So Check the following :-
Rapid Setup → Configuration → Joiner
Is Exclude Uncorrelated Identities ON?
Any Trigger Filters that the new identities don’t meet?
On the identity: confirm it has an authoritative account link (correlated). If it’s uncorrelated, Rapid Setup will skip it when that option is enabled
If you need to re-queue after fixing config, set the identity’s state back to needed (or clear it) and run an Identity Refresh / event processing so it can move to processed when it runs.