Server Side loggin (stopped working ) - BullHorn/App Connect 2.0

Hi ​@Mber You can try to re-save server side logging to make it refresh authorization. It may be caused by authorization lost. 

If it still can’t work, can you help to collect logs and send to the email that I sent in private message
 

Steps to collect logs:

1. Right click at the app and select Inspect to open Chrome developer tool.
2. Keep the developer tool open. Then go to setting logout in the page bottom and re-login RingCentral account
3. Go to Setting to auth Bullhorn. Then go to admin and server side setting logging setting.
4. Enable the server side logging and save to enable it.
5. Go to developer tool's console panel, right click at logs to save all as file.
6. Go to developer tool's network panel, click download icon to download HAR file.

Updates: We just identified and fixed a bug that happened when user mapping is not setup. Can you help to check if your server side logging works now?

​@Mber Wanted to make sure you saw the above comment from ​@Embbnux 

My apologies. I didnt receive a notification that a message was sent. No this is still not working for me.

Thanks ​@Mber for the information. I see your private message that you sent a email. I check in inbox and spam email, but I still can’t get that. It maybe blocked in your email system. Can you help check and sent it again without attachment files, maybe a google drive shared link?

Updates: we confirm the issue is caused by a long chars for “default note action” bullhorn setting. Bullhorn only allows max 30 length for default note chars. If user set a long default note action, it will reject the call log request. 
We will update UI to limit long default note action input. For quick fixes, user needs to avoid to set a default note > 30 chars.