We have successfully migrated the majority of object IDs, but we are encountering an issue with threads created by certain emails. These threads are not being translated, and we are receiving the following error from the Nylas translation API:
400/26012: Failed to translate Nylas resource ID to Provider resource ID with the message: ‘v2 response: We cannot translate EAS IDs, for requested account xxxxxxxxxx in V2 Application xxxxxxxxxx.’
While we understand that threads associated with EAS emails cannot be translated, this data is critical as we are providing a service to our client.
Could you please suggest a way to migrate these object IDs to V3 without losing our email data?
Has anyone else encountered a similar issue? Any advice or guidance on how to resolve this would be greatly appreciated.
I’m reaching out again as I haven’t received any responses to my previous post and I’m hoping someone might be able to provide guidance.
We are still facing an issue during our migration from V2 object IDs to V3 using the Object Migration Endpoint. While the majority of our object IDs have successfully migrated, we are encountering an issue with threads created by certain emails, specifically those linked to EAS accounts. The error we’re seeing is:
400/26012: Failed to translate Nylas resource ID to Provider resource ID with the message: ‘v2 response: We cannot translate EAS IDs, for requested account xxxxxxxxxx in V2 Application xxxxxxxxxx.’
I understand that EAS IDs cannot be translated, but this data is critical for the service we are providing to our client. Has anyone else encountered this problem? Is there a solution or workaround to migrate these object IDs to V3 without losing the email data?
Any help or advice would be greatly appreciated. Thank you in advance.