Failed to Connect or Import Okta Data: Cannot get property 'statusAndThresholdConfig' on null object

[aainte]

Our okta import job started failing no changes has been made. getting the Error - Failed to Connect or Import Okta Data :
Cannot get property 'statusAndThresholdConfig' on
null object

side note: we currently upgraded to 24.5 not sure if there is a correlation.  is anyone seeing similar issue? any guidance is greatly appreciated.

[NM]

Hi @aainte if the issue started happening after upgrade then raise a ticket for them same.

[rushikeshvartak]

Please share connection config screenshot.

[aainte]

@NM it started a little before the upgrade. i don't think it has to do with the upgrade. 

[aainte]

@rushikeshvartak here is the screenshots of our connection which is the out of the box okta connector. the funny thing is we have test environment same config, and the import job is working there. 

[NM]

@aainte share logs

[aainte]

@NM here is the logs:

[aainte]

@NM the job failure response 

[rushikeshvartak]

What is connector type?

[aainte]

This is the okta out of the box connector to import accounts and groups

[rushikeshvartak]

Did you added STATUS_THRESHOLD_CONFIG in connector

[aainte]

@rushikeshvartak, yes, it's part of the screen shots of the connector i shared here

[rushikeshvartak]

Remove config and retry

[aainte]

@rushikeshvartak  tried your suggestion. removed the config and retried. still get the same error. restarted the app and still getting the same error 

[rushikeshvartak]

• Raise support ticket as this issue occurred after upgrade 

[sealchan · Accepted solution]

I've noticed that your configuration USERFIELDMAPPINGS and APPACCOUNTFIELDMAPPINGS conforms to the documented configuration for v2022...but those configuration formats have changed in later versions:

v2022

https://docs.saviyntcloud.com/bundle/Okta-v2022x/page/Content/Creating-an-integration.htm

v2024

https://docs.saviyntcloud.com/bundle/Okta-v24x/page/Content/Creating-an-integration.htm#Creating4

USERFIELDMAPPINGS
This, like ACCOUNTFIELDMAPPINGS is a comma-delimited list which you have but your USERFIELDMAPPINGS ends with a semicolon. Try removing the semicolon

APPACOUNTFIELDMAPPING
This field is now a JSON. You still have it as a comma-delimited list

[rushikeshvartak]

Comma works just validated.

@aainte  - You need to put account mapping on new line each one

[aainte]

Thank you all for the support. @sealchan suggestion was the solution. 

[aainte]

the AppAccountFieldMapping was the issue. removing it fixed the job. going forward we are going to make it json format.