Sync 2nd time fails even after download succeeded

Connector Questions & Issues
1

→

  • Is this your first time deploying Airbyte?: No
  • OS Version / Instance: Windows
  • Memory / Disk: you can use something like 16Gb / 1 Tb
  • Deployment: Docker
  • Airbyte Version: VERSION=0.40.18
  • Source name/version: Redshift/file
  • Destination name/version: custom local csv destination
  • Step: after initial sync succeeds, The issue is happening during next sync
  • Description: Facing such error in logs after the download is “SUCCEEDED”.

2022-12-15 13:17:28 WARN i.t.i.w.ActivityWorker$TaskHandlerImpl(logExceptionDuringResultReporting):365 - Failure during reporting of activity result to the server. ActivityId = 572543e4-4b6a-3c21-87d3-f9986f3656c5, ActivityType = JobSuccessWithAttemptNumber, WorkflowId=connection_manager_457b6ad6-4826-4fb1-93c8-d93b8a4687d0, WorkflowType=ConnectionManagerWorkflow, RunId=823444ac-dc24-4e64-8dd5-f0b2fd32ee35 io.grpc.StatusRuntimeException: NOT_FOUND: invalid activityID or activity already timed out or invoking workflow is completed 2022-12-15 13:17:37 WARN i.t.i.a.ActivityTaskExecutors$BaseActivityTaskExecutor(execute):114 - Activity failure. ActivityId=572543e4-4b6a-3c21-87d3-f9986f3656c5, activityType=JobSuccessWithAttemptNumber, attempt=2 java.lang.IllegalStateException: Transitioning Job 14 from JobStatus SUCCEEDED to SUCCEEDED is not allowed. The only valid statuses that an be transitioned to from SUCCEEDED are []

This is preventing me to triggerin the sync again.
Trigger api gives below error:

{‘message’: ‘A sync is already running for: 836a4c9a-7c07-40dc-b253-1937026c0db9’, ‘exceptionClassName’: ‘io.airbyte.server.errors.ValueConflictKnownException’, ‘exceptionStack’: [‘io.airbyte.server.errors.ValueConflictKnownException: A sync is already running for: 836a4c9a-7c07-40dc-b253-1937026c0db9’,}

We are Running airbyte in docker
VERSION=0.40.18

I can not trigger the connection but check status api shows it succeeded. (edited)
Error appears after successful notification.

2022-12-16 12:59:17 INFO i.a.n.SlackNotificationClient(notify):135 - Successful notification (200): { "data": { "text": "Your connection from Redshift to Custom Destination succeeded\nThis was for sync started on Friday, December 16, 2022 at 12:56:59 PM Coordinated Universal Time, running for 29 seconds.\n\nYou can access its logs here: http://localhost:8000/workspaces/fbe5f287-5a01-4bd1-b61a-7167b083f43f/connections/a38c7ff6-915b-49f5-ae3e-31c46f78542d\n\nJob ID: 25" }, "status": { "code": 200, "result": "success" } } 2022-12-16 12:59:17 WARN i.t.i.w.ActivityWorker$TaskHandlerImpl(logExceptionDuringResultReporting):365 - Failure during reporting of activity result to the server. ActivityId = c2dfb20c-4f4a-316b-9737-666d0dd30606, ActivityType = JobSuccessWithAttemptNumber, WorkflowId=connection_manager_a38c7ff6-915b-49f5-ae3e-31c46f78542d, WorkflowType=ConnectionManagerWorkflow, RunId=97d25f14-9bbe-4e5d-bd1b-deae19d88c56 io.grpc.StatusRuntimeException: NOT_FOUND: invalid activityID or activity already timed out or invoking workflow is completed

2

Hello there! You are receiving this message because none of your fellow community members has stepped in to respond to your topic post. (If you are a community member and you are reading this response, feel free to jump in if you have the answer!) As a result, the Community Assistance Team has been made aware of this topic and will be investigating and responding as quickly as possible.
Some important considerations that will help your to get your issue solved faster:

  • It is best to use our topic creation template; if you haven’t yet, we recommend posting a followup with the requested information. With that information the team will be able to more quickly search for similar issues with connectors and the platform and troubleshoot more quickly your specific question or problem.
  • Make sure to upload the complete log file; a common investigation roadblock is that sometimes the error for the issue happens well before the problem is surfaced to the user, and so having the tail of the log is less useful than having the whole log to scan through.
  • Be as descriptive and specific as possible; when investigating it is extremely valuable to know what steps were taken to encounter the issue, what version of connector / platform / Java / Python / docker / k8s was used, etc. The more context supplied, the quicker the investigation can start on your topic and the faster we can drive towards an answer.
  • We in the Community Assistance Team are glad you’ve made yourself part of our community, and we’ll do our best to answer your questions and resolve the problems as quickly as possible. Expect to hear from a specific team member as soon as possible.

Thank you for your time and attention.
Best,
The Community Assistance Team

3

Hi Sheshan!

I see you’ve already brought up this issue in Slack:
https://airbytehq-team.slack.com/archives/C021JANJ6TY/p1671110541727019

Looks like you’re still on version 0.40.18, are you able to update to the current version?

Please review our code of conduct, double posting a single question goes against it. Here is the full rule:

Rule 3: Don’t double-post.
Please be considerate of our community members’ time. We know your question is important, but please keep in mind that Airbyte Slack is not a customer service platform but a community of volunteers who will help you as they are able around their own work schedule. You have access to all the history, so it’s easy to check if your question has already been asked.

Please make sure to read through the full code of conduct:
https://docs.airbyte.com/project-overview/slack-code-of-conduct/

I am closing this thread, and will wait for your reply in Slack after updating to the current version.

Thank you,
Nataly