tap-freshdesk icon indicating copy to clipboard operation
tap-freshdesk copied to clipboard

ERROR | tap-freshdesk | An unhandled error occurred while syncing 'tickets_abridged'

Open Prashantvik opened this issue 1 year ago • 0 comments

Issue Description: Unhandled Error Encountered While Syncing 'tickets_abridged' in Meltano

Problem Statement: An unhandled error is occurring during the synchronization process of the 'tickets_abridged' data stream while transferring data from Freshdesk to Snowflake using Meltano's tap-freshdesk and target-snowflake connectors. The issue arises specifically when executing the sync operation, resulting in a FatalAPIError being raised with the associated error message.

Error Message:

raise FatalAPIError(msg)
[info] singer_sdk.exceptions.FatalAPIError: 400 Client Error: Bad Request for path: /api/v2/tickets

Detailed Description: Upon initial execution, the data transfer process successfully moves a significant portion of the data for all other schemas and failed for tickets_abridged after moving few thousand records leading to incomplete data synchronization. Even after re-running the operation, only a fraction of the remaining data for tickets_abridged is getting transferred before encountering the same error again.

Log Details:

  • File Path: /project/.meltano/extractors/tap-freshdesk/venv/lib/python3.9/site-packages/singer_sdk/streams/core.py
  • Line Numbers:
    • Line 1175: sync() method call within core.py
    • Line 1070: _sync_records() method call within core.py
    • Line 60: get_records() method call within streams.py
    • Line 397: request_records() method call within rest.py
  • Error Trace:
    • The error is raised at resp = decorated_request(prepared_request, context) within rest.py.
    • This ultimately leads to the FatalAPIError being raised, halting the synchronization process.

Request for Assistance: Seeking guidance or assistance from the community or relevant stakeholders who might have encountered a similar issue or possess expertise in resolving such errors.

Additional Context: Providing any additional information or context surrounding the issue, such as relevant configuration settings or environment details, may aid in troubleshooting and resolving the error effectively.

Conclusion: As this issue impedes the successful synchronization of data between Freshdesk and Snowflake, prompt resolution is essential to ensure uninterrupted data flow and maintain system integrity.

Acknowledgment of Community Input: Gratitude for any insights, suggestions, or solutions provided by the community members or project contributors in addressing this issue.

Prashantvik avatar Feb 29 '24 07:02 Prashantvik