Announcing the SAVIYNT KNOWLEDGE EXCHANGE unifying the Saviynt forums, documentation, training, and more in a single search tool across platforms. Click HERE to read the Announcement.

Issues With Email Server Settings - OAuth Based

Sivagami
Valued Contributor
Valued Contributor

Email History Job Error:

I have encountered 400 and 429 errors in logs when running email history job. The job in job control panel shows the status as Success though.

Looks like 429 error is due to rate limiting on Microsoft Graph API side. Are we receiving 429 due to the below config enabled in Global Configuration? Any suggestion on the best practice?

Sivagami_0-1676319068587.png

IncomingMailArsJob Error:

I couldn't find any error in logs but the incomingMailArsJob is failing in job control panel. How can I debug this further? 

Error in processEmailReceivednull

 

-Siva

5 REPLIES 5

rushikeshvartak
All-Star
All-Star

100 threads seems to big number. How frequent job is running ?

https://learn.microsoft.com/en-us/graph/throttling-limits


Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.

Sivagami
Valued Contributor
Valued Contributor

I actually disabled the config of using threads (Unchecked Use Threads to Send email via email history job) which stopped 429 error in logs but still see 400. Client ID and Client secret are correct and Save & Test connection is successful as well. Not sure what is missing which is causing the error.

2023-02-14 10:29:39,341 [quartzScheduler_Worker-28] ERROR services.EmailerService - Exception in pullObjectsByRest : 400
2023-02-14 10:29:39,655 [quartzScheduler_Worker-28] ERROR services.EmailerService - Exception in pullObjectsByRest : 400
2023-02-14 10:29:39,968 [quartzScheduler_Worker-28] ERROR services.EmailerService - Exception in pullObjectsByRest : 400
2023-02-14 10:29:40,337 [quartzScheduler_Worker-28] ERROR services.EmailerService - Exception in pullObjectsByRest : 400
2023-02-14 10:29:40,591 [quartzScheduler_Worker-28] ERROR services.EmailerService - Exception in pullObjectsByRest : 400
2023-02-14 10:29:40,894 [quartzScheduler_Worker-28] ERROR services.EmailerService - Exception in pullObjectsByRest : 400
2023-02-14 10:29:40,894 [quartzScheduler_Worker-28] ERROR services.EmailerService - Exception in token refresh : 400
2023-02-14 10:29:41,044 [quartzScheduler_Worker-28] ERROR services.EmailerService - Exception in pullObjectsByRest : 400
2023-02-14 10:29:41,386 [quartzScheduler_Worker-28] ERROR services.EmailerService - Exception in pullObjectsByRest : 400
2023-02-14 10:29:41,717 [quartzScheduler_Worker-28] ERROR services.EmailerService - Exception in pullObjectsByRest : 400
2023-02-14 10:29:42,034 [quartzScheduler_Worker-28] ERROR services.EmailerService - Exception in pullObjectsByRest : 400
2023-02-14 10:29:42,467 [quartzScheduler_Worker-28] ERROR services.EmailerService - Exception in pullObjectsByRest : 400
2023-02-14 10:29:42,822 [quartzScheduler_Worker-28] ERROR services.EmailerService - Exception in pullObjectsByRest : 400
2023-02-14 10:29:42,822 [quartzScheduler_Worker-28] ERROR services.EmailerService - Exception in token refresh : 400
2023-02-14 10:29:42,974 [quartzScheduler_Worker-28] ERROR services.EmailerService - Exception in pullObjectsByRest : 400
2023-02-14 10:29:43,377 [quartzScheduler_Worker-28] ERROR services.EmailerService - Exception in pullObjectsByRest : 400
2023-02-14 10:29:43,703 [quartzScheduler_Worker-28] ERROR services.EmailerService - Exception in pullObjectsByRest : 400
2023-02-14 10:29:44,043 [quartzScheduler_Worker-28] ERROR services.EmailerService - Exception in pullObjectsByRest : 400
2023-02-14 10:29:44,403 [quartzScheduler_Worker-28] ERROR services.EmailerService - Exception in pullObjectsByRest : 400
2023-02-14 10:29:44,706 [quartzScheduler_Worker-28] ERROR services.EmailerService - Exception in pullObjectsByRest : 400
2023-02-14 10:29:44,708 [quartzScheduler_Worker-28] ERROR services.EmailerService - Exception in token refresh : 400

AS5278
Regular Contributor II
Regular Contributor II

Hi @Sivagami ,

Was this issue solved?. If yes how?

xurde

Sivagami
Valued Contributor
Valued Contributor

@AS5278 - Basically if the recipient email is not a valid (or) for some reason your toaddress / ccaddress computes to null, then calling microsoft graph API fails with 400 bad request & Saviynt thinks it's an auth issue & tries to refresh the token. I believe this is the reason for the 400 error in logs

Hi @Sivagami ,

We switched to Oauth based email server config 2 days ago and also noticed the same. But apart from this, we observed that we are not receiving any emails with attachments (like analytics report emails). Tested in dev as well, emails with attachments not being received.

Can you confirm if you are receiving emails with attachments? and if you faced this issue, do you know about the resolution?

Thanks


Thanks & Regards,
Haardik Verma