SCIM import: user.lifecycle.create returns 500 with empty error reason on confirm

Questions SCIM
1
  1. Org: trial-8780899
  2. What fails: Confirming an imported user (app-sourced import, SAML 2.0 + SCIM app) throws a 500 on user creation.
  3. Event: user.lifecycle.create, outcome.result: FAILURE, outcome.reason: null, errorMessage: "" — no reason recorded.
  4. Request ID: b29df85c4d3b199a2418d518bbbdce68
  5. Transaction ID: b29df85c4d3b199a2418d518bbbdce68
  6. Timestamp (UTC): 2026-06-23T06:31:06.680Z
  7. App instance ID: 0oa14170iq8zADkbH698
  8. Key detail that makes this their problem: the preceding system.import.user_match.confirm event succeeds (INFO), the import preview shows the user parsed cleanly (name/username/email all populated), and the only failing step is user.lifecycle.create with an empty error reason. So it’s not config or data — the create faults internally with nothing logged.
2

Hi,

Do you have more than 10 users in your org? Even if you have deactivated users, I suggest you delete all users [the number of users should be less than 10] and then check whether the user import is successful.

3

As the system.import.user_match.confirm completes successfully and the import preview contains valid user attributes, it does seem like the SCIM import pipeline is reaching the user creation step correctly. A user.lifecycle.create failure with a 500 an empty outcome.reason, and no errorMessage usually points to an internal service-side failure rather than malformed SCIM data. If you haven’t already, I would suggest open a support case with the Request ID and Transaction ID you included so Okta can trace the backend logs. It would also be useful to check whether the same behavior occurs with a different test user or a fresh app instance to rule out any tenant-specific issue, but based on the empty error details, this doesn’t look like a configuration problem on your side.