Locale of error message

Hi Megumi! We have different error handling based on the specific APIs that are being called, so could you please provide the API calls and any payloads that you're passing in when you're seeing these discrepancies?

Thanks Greg,

API which contains the error message is 

GET /api/v2/job_statuses/{jobId}.json

Original jobs are from these APIs.

/api/v2/users/create_or_update_many.json

/api/v2/users/destroy_many.json

The error messages in the "results" of the job statuses are like

{'id': xxxxxxxxxxxx, 'error': 'UserDeleteError', 'details': 'O usuário é o solicitante em 1 ticket, que não está fechado.'}

{'id': xx, 'error': 'UserUpdateError', 'details': 'xx xx: 이메일: xxxx@xxxxxx은(는) 이미 다른 사용자가 사용하고 있습니다.', 'status': 'Failed'}

Hi Megumi, thank you for sharing that! I've done some research and it appears that the error will be thrown in the default language of the user where the issue occurred. Can you confirm this with the errors that you shared above?

Thank you for response Greg.

No, the language of the error was not the default language of the user. The API was executed by admin whose default language is Japanese, and the target end-user had also Japanese as default language. 

I repeated the same request and the error came in different languages.

curl -X POST "https://con-eclect-nakamura.zendesk.com/api/v2/users/create_or_update_many.json" -d ...

---------------------
< date: Mon, 22 Mar 2021 02:31:39 GMT
< x-zendesk-api-version: v2
< x-zendesk-application-version: v8356.50
< x-zendesk-origin-server: classic-app-server-5b89d97745-tdlsl
< x-request-id: 633c014448230b8f-IAD

https://con-eclect-nakamura.zendesk.com/api/v2/job_statuses/fc2265e24ce1feccdfd89a99209f4109.json
=> Japanese

---------------------
< date: Mon, 22 Mar 2021 02:32:14 GMT
< x-zendesk-api-version: v2
< x-zendesk-application-version: v8356.50
< x-zendesk-origin-server: classic-app-server-5b89d97745-2smdc
< x-request-id: 633c022079c41d73-IAD

https://con-eclect-nakamura.zendesk.com/api/v2/job_statuses/393809816e02ee77588dacff77b9f64f.json
=> English

---------------------
< date: Mon, 22 Mar 2021 02:34:54 GMT
< x-zendesk-api-version: v2
< x-zendesk-application-version: v8356.50
< x-zendesk-origin-server: classic-app-server-5b89d97745-nmgch
< x-request-id: 633c06088dc71d5f-IAD

https://con-eclect-nakamura.zendesk.com/api/v2/job_statuses/23bb00c56fbf45e99ceabdc3883fe9ca.json
=> Portuguese

Thank you for sharing that...that helps us try and narrow this down a bit more, although the root cause is still eluding us. Just so that we have a better idea of how to narrow this down:

• Does this occur every time you try to call the job status endpoint?
• Do you do anything different when this issue does present itself?
• Have you seen any patterns at all to the timing?
• I see that around that same time, there were a number of other calls to the job status endpoint...did those all return correctly in Japanese?

Thank you for investigating.

> Does this occur every time you try to call the job status endpoint?

Yes, they were always the job status endpoint when I noticed this issue.

> Do you do anything different when this issue does present itself?

No, I didn't do any special thing. I just repeated on a terminal.

> Have you seen any patterns at all to the timing?

No, I didn't find any patterns. 

> I see that around that same time, there were a number of other calls to the job status endpoint...did those all return correctly in Japanese?

They were mostly in English when I tried yesterday. The order was Japanese, English many times, Portuguese, English many times. 

I saw Japanese or English many times in error messages in job statuses. The other languages such as Portuguese or Korean are rare case, I think. But some customers wants to know why the language differs.

Ok, great, thanks again for that information. I was talking with some of our engineers yesterday and they had created a fix for this in a different area in the past and they'd like to investigate it here to see if it follows the same pattern. As such, I'm going to get a new ticket started for you and create a problem ticket for that team to begin the investigation.

I'm hopeful that they will be able to find something soon, so as soon as they do, I'll update you in that ticket. Once we have a full resolution here, I'll also update this post in case anyone else is experiencing this.

Thanks for all of the help getting to the root of this so far!

Thanks Greg. I got the ticket.