Sync status marked as FAILED despite successful data transfer – Cannot invoke "java.lang.Integer.intValue()" error

[oxlngo]

Topic

Custom connector sync status error

Relevant information

I've developing a custom source connector for SQL Server and a custom destination connector that sends data to an HTTP API. The data sync completes successfully — records are pulled from the source and sent to the destination — but the sync status is marked as FAILED in the Airbyte UI.

Error message: Cannot invoke "java.lang.Integer.intValue()" because the return value of "java.util.Map.get(Object)" is null
Has anyone encountered this issue before or know what might be causing it?

here is the log

2025-04-02 11:09:35 info failures: [ {
  "failureOrigin" : "replication",
  "internalMessage" : "Cannot invoke \"java.lang.Integer.intValue()\" because the return value of \"java.util.Map.get(Object)\" is null",
  "externalMessage" : "Something went wrong during replication",
  "metadata" : {
    "attemptNumber" : 0,
    "jobId" : 45
  },
  "stacktrace" : "java.lang.NullPointerException: Cannot invoke \"java.lang.Integer.intValue()\" because the return value of \"java.util.Map.get(Object)\" is null\n\tat io.airbyte.workers.models.StateWithId.getIdFromStateMessage(StateWithId.java:36)\n\tat io.airbyte.workers.internal.bookkeeping.streamstatus.StreamStatusTracker.trackStreamState(StreamStatusTracker.kt:138)\n\tat io.airbyte.workers.internal.bookkeeping.streamstatus.StreamStatusTracker.trackStream(StreamStatusTracker.kt:79)\n\tat io.airbyte.workers.internal.bookkeeping.streamstatus.StreamStatusTracker.track(StreamStatusTracker.kt:51)\n\tat io.airbyte.workers.general.ReplicationWorkerHelper.internalProcessMessageFromDestination(ReplicationWorkerHelper.kt:442)\n\tat io.airbyte.workers.general.ReplicationWorkerHelper.processMessageFromDestination(ReplicationWorkerHelper.kt:316)\n\tat io.airbyte.workers.general.BufferedReplicationWorker.readFromDestination(BufferedReplicationWorker.java:491)\n\tat io.airbyte.workers.general.BufferedReplicationWorker.lambda$runAsync$2(BufferedReplicationWorker.java:216)\n\tat java.base/java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1804)\n\tat java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)\n\tat java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)\n\tat java.base/java.lang.Thread.run(Thread.java:1583)\n",
  "timestamp" : 1743606515332
}, {
  "failureOrigin" : "replication",
  "internalMessage" : "io.airbyte.workers.exception.WorkerException: Destination has not terminated.  This warning is normal if the job was cancelled.",
  "externalMessage" : "Something went wrong during replication",
  "metadata" : {
    "attemptNumber" : 0,
    "jobId" : 45
  },
  "stacktrace" : "java.lang.RuntimeException: io.airbyte.workers.exception.WorkerException: Destination has not terminated.  This warning is normal if the job was cancelled.\n\tat 

[marcosmarxm]

Please use the right template for report problem with connectors.