@kapa.ai getting this error when running the jira connector 2026-10-26 065032 replication-orchestrator INFO failures: [ { "failureOrigin" : "destination", "failureType" : "system_error", "internalMessage" : "tech.allegro.schema.json2avro.converter.AvroConversionException: Failed to convert JSON to Avro: Could not evaluate union, field lead is expected to be one of these: NULL, STRING. If this is a complex type, check if offending field (path: lead) adheres to schema: {self=saasxl.atlassian.net/rest/api/3/user?accountId=…, accountId=712020:e91d92a4-60fc-4e8d-b494-6348ad63a6c7, accountType=atlassian, avatarUrls={48x48=, 24x24=, 16x16=, 32x32=}, displayName=Jyotish, active=true}", "externalMessage" : "Something went wrong in the connector. See the logs for more details.", "metadata" : { "attemptNumber" : 4, "jobId" : 22459, "from_trace_message" : true, "connector_command" : "write" }, "stacktrace" : "tech.allegro.schema.json2avro.converter.AvroConversionException: Failed to convert JSON to Avro: Could not evaluate union, field lead is expected to be one of these: NULL, STRING. If this is a complex type, check if offending field (path: lead) adheres to schema: {self=saasxl.atlassian.net/rest/api/3/user?accountId=…, accountId=712020:e91d92a4-60fc-4e8d-b494-6348ad63a6c7, accountType=atlassian, avatarUrls={48x48=, 24x24=, 16x16=, 32x32=}, displayName=Jyotish, active=true}\n\tat tech.allegro.schema.json2avro.converter.JsonGenericRecordReader.read(JsonGenericRecordReader.java:131)\n\tat tech.allegro.schema.json2avro.converter.JsonGenericRecordReader.read(JsonGenericRecordReader.java:120)\n\tat tech.allegro.schema.json2avro.converter.JsonAvroConverter.convertToGenericDataRecord(JsonAvroConverter.java:95)\n\tat io.airbyte.cdk.integrations.destination.s3.avro.AvroRecordFactory.getAvroRecord(AvroRecordFactory.java:39)\n\tat io.airbyte.cdk.integrations.destination.s3.parquet.ParquetSerializedBuffer.accept(ParquetSerializedBuffer.java:97)\n\tat io.airbyte.cdk.integrations.destination.record_buffer.SerializedBufferingStrategy.addRecord(SerializedBufferingStrategy.java:73)\n\tat io.airbyte.cdk.integrations.destination.buffered_stream_consumer.BufferedStreamConsumer.acceptTracked(BufferedStreamConsumer.java:205)\n\tat io.airbyte.cdk.integrations.base.FailureTrackingAirbyteMessageConsumer.accept(FailureTrackingAirbyteMessageConsumer.java:65)\n\tat io.airbyte.cdk.integrations.base.Destination$ShimToSerializedAirbyteMessageConsumer.consumeMessage(Destination.java:115)\n\tat io.airbyte.cdk.integrations.base.Destination$ShimToSerializedAirbyteMessageConsumer.accept(Destination.java:91)\n\tat io.airbyte.cdk.integrations.base.IntegrationRunner.consumeWriteStream(IntegrationRunner.java:321)\n\tat io.airbyte.cdk.integrations.base.IntegrationRunner.consumeWriteStream(IntegrationRunner.java:301)\n\tat io.airbyte.cdk.integrations.base.IntegrationRunner.runInternal(IntegrationRunner.java:190)\n\tat io.airbyte.cdk.integrations.base.IntegrationRunner.run(IntegrationRunner.java:125)\n\tat io.airbyte.integrations.destination.gcs.GcsDestination.main(GcsDestination.java:16)\n\tSuppressed: java.lang.NullPointerException: Cannot invoke \"java.io.InputStream.close()\" because \"this.inputStream\" is null\n\t\tat io.airbyte.cdk.integrations.destination.s3.parquet.ParquetSerializedBuffer.close(ParquetSerializedBuffer.java:163)\n\t\tat io.airbyte.cdk.integrations.destination.record_buffer.SerializedBufferingStrategy.close(SerializedBufferingStrategy.java:159)\n\t\tat io.airbyte.cdk.integrations.destination.buffered_stream_consumer.BufferedStreamConsumer.close(BufferedStreamConsumer.java:301)\n\t\tat io.airbyte.cdk.integrations.base.FailureTrackingAirbyteMessageConsumer.close(FailureTrackingAirbyteMessageConsumer.java:82)\n\t\tat io.airbyte.cdk.integrations.base.Destination$ShimToSerializedAirbyteMessageConsumer.close(Destination.java:96)\n\t\tat io.airbyte.cdk.integrations.base.IntegrationRunner.runInternal(IntegrationRunner.java:189)\n\t\t... 2 more\nCaused by: org.apache.avro.AvroTypeException: Could not evaluate union, field lead is expected to be one of these: NULL, STRING. If this is a complex type, check if offending field (path: lead) adheres to schema: {self=saasxl.atlassian.net/rest/api/3/user?accountId=…, accountId=712020:e91d92a4-60fc-4e8d-b494-6348ad63a6c7, accountType=atlassian, avatarUrls={48x48=, 24x24=, 16x16=, 32x32=}, displayName=Jyotish, active=true}\n\tat tech.allegro.schema.json2avro.converter.AvroTypeExceptions.unionException(AvroTypeExceptions.java:16)\n\tat tech.allegro.schema.json2avro.converter.JsonGenericRecordReader.readUnion(JsonGenericRecordReader.java:304)\n\tat tech.allegro.schema.json2avro.converter.JsonGenericRecordReader.read(JsonGenericRecordReader.java:198)\n\tat tech.allegro.schema.json2avro.converter.JsonGenericRecordReader.read(JsonGenericRecordReader.java:172)\n\tat tech.allegro.schema.json2avro.converter.JsonGenericRecordReader.lambda$readRecord$0(JsonGenericRecordReader.java:154)\n\tat java.base/java.util.LinkedHashMap.forEach(LinkedHashMap.java:986)\n\tat tech.allegro.schema.json2avro.converter.JsonGenericRecordReader.readRecord(JsonGenericRecordReader.java:143)\n\tat tech.allegro.schema.json2avro.converter.JsonGenericRecordReader.read(JsonGenericRecordReader.java:129)\n\t... 14 more\n", "timestamp" : 1793011772220 }, { "failureOrigin" : "destination", "internalMessage" : "Destination process exited with non-zero exit code 1", "externalMessage" : "Something went wrong within the destination connector", "metadata" : { "attemptNumber" : 4, "jobId" : 22459, "connector_command" : "write" }failureOrigin" : "replication", "internalMessage" : "io.airbyte.workers.exception.WorkerException: Destination process exit with code 1. This warning is normal if the job was cancelled.", "externalMessage" : "Something went wrong during replication", "metadata" : { "attemptNumber" : 4, "jobId" : 22459 }, "stacktrace" : "java.lang.RuntimeException: io.airbyte.workers.exception.WorkerException: Destination process exit with code 1. This warning is normal if the job was cancelled.\n\tat io.airbyte.workers.general.BufferedReplicationWorker$CloseableWithTimeout.lambda$close$0(BufferedReplicationWorker.java:548)\n\tat io.airbyte.workers.general.BufferedReplicationWorker.lambda$runAsyncWithTimeout$5(BufferedReplicationWorker.java:244)\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)\nCaused by: io.airbyte.workers.exception.WorkerException: Destination process exit with code 1. This warning is normal if the job was cancelled.\n\tat io.airbyte.workers.internal.LocalContainerAirbyteDestination.close(LocalContainerAirbyteDestination.kt:61)\n\tat io.airbyte.workers.general.BufferedReplicationWorker$CloseableWithTimeout.lambda$close$0(BufferedReplicationWorker.java:546)\n\t... 5 more\n", "timestamp" : 1793011772506 } ] any issue in the source credential ?

Thinking completed Schema Mismatch Error — Not a Credential Issue This error is not related to your source credentials. It's a schema mismatch between what the Jira connector is sending and what the destination expects. What's happening The error message is clear: >

Could not evaluate union, field lead is expected to be one of these: NULL, STRING

The destination (GCS, writing Parquet/Avro format) has a cached/existing schema where the

lead

field in the

project_components

stream is typed as

NULL | STRING

. However, the Jira API is now returning

lead

as a complex object (with fields like

accountId

,

displayName

,

avatarUrls

,

active

, etc.). Looking at the connector's manifest, the

lead

field is indeed defined as an object with multiple properties (e.g.,

accountId

,

accountType

,

displayName

,

avatarUrls

, etc.). [manifest.yaml] Root Cause The destination has an outdated Avro/Parquet schema for the

project_components

stream that defines

lead

as a simple string, but the actual data coming from Jira contains a full user object. How to fix it 1. Refresh the connection schema: In Airbyte, go to your connection → Schema tab → click Refresh source schema to pick up the latest schema definition. 2. Reset the stream: After refreshing, you may need to perform a Reset on the

project_components

stream (or the full connection) so the destination recreates the table/file with the correct schema. ◦ Go to your connection → Settings → Reset streams (or reset just the affected stream if your Airbyte version supports per-stream resets). 1. Re-sync: Run a full sync after the reset. This will allow the destination to recreate the schema with

lead

as an object rather than a string, resolving the Avro conversion failure. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

we have not enabled that stream inthe job

Thinking completed Looking at the error more carefully, the stream involved is actually from the

projects

stream, not

project_components

. The

lead

field in the

projects

schema is defined without a type (no explicit

type: object

or

type: string

), which can cause schema inference issues. [manifest.yaml] The error originates at the destination side (GCS writing Parquet), where the Avro schema for the

lead

field was previously inferred as

NULL | STRING

, but Jira is now returning it as a full user object. Possible causes even without the stream explicitly enabled • The schema for the

projects

stream may have been previously synced and the destination has an older schema cached. • The

projects

stream may be a parent stream that is implicitly synced to support other enabled streams (e.g., issues, sprints, etc. often depend on project data). Recommended steps 1. Check which streams are actually running — verify in the sync logs whether

projects

is being synced as a dependency of another enabled stream. 2. Refresh the source schema on the connection. 3. Reset the

projects

stream specifically to force the destination to recreate the schema with the correct structure for

lead

. 4. Re-run the sync. The knowledge sources do not contain enough detail about your specific Airbyte version's stream dependency behavior to say definitively which stream is triggering this, so I'd recommend checking the full sync logs to confirm the exact stream name involved. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

why the datatype is unknown here

Thinking completed Why lead Shows as "Unknown" Type Looking at your screenshot, the

lead

field in the projects stream is showing as Unknown because the field is defined as a complex object in the Jira connector's schema, but Airbyte's UI displays

Unknown

when it cannot map the field's type to one of its standard recognized types (String, Boolean, Array, Object, etc.). The

lead

field contains a full user object with nested properties like

accountId

,

displayName

,

avatarUrls

,

active

, etc. [manifest.yaml] This is directly related to your earlier error — the destination (GCS/Avro) previously stored

lead

as

NULL | STRING

, but the actual data coming from Jira is a nested object, causing the Avro conversion to fail. Why "Unknown" specifically? The

lead

field's schema likely lacks an explicit top-level

type

declaration in the connector manifest, so Airbyte cannot confidently classify it into a known simple type — hence it shows as

Unknown

in the UI. What you should do 1. Reset the

projects

stream — this forces the destination to drop and recreate the schema correctly. 2. Re-sync — the

lead

field will then be written as an object/JSON rather than a string, resolving the Avro conversion error. The

Unknown

type itself is not necessarily a blocker, but combined with an outdated destination schema, it causes the sync failure you're seeing. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

what need to done here

Thinking completed Steps to Fix the Sync Failure Based on your screenshot, the

projects

stream is enabled and the

lead

field is typed as

Unknown

. Here's what you need to do: 1. Refresh the Source Schema • Go to your connection Schema tab • Click Refresh source schema to pull the latest schema from Jira 2. Reset the projects Stream • Go to Settings tab of the connection • Find the option to Reset streams • Reset specifically the

projects

stream (or all streams if per-stream reset is not available) • This forces the destination (GCS) to drop and recreate the Avro/Parquet schema with the correct structure for the

lead

field 3. Save and Re-sync • Save your changes • Trigger a new sync Why this is necessary The destination currently has an outdated schema where

lead

is stored as

NULL | STRING

. After the reset, it will be recreated correctly as a nested object, which matches what Jira is actually returning — resolving the

AvroConversionException

you're seeing. > ⚠️ Note: Resetting a stream will clear the existing data for that stream in the destination and perform a full re-sync. Make sure this is acceptable before proceeding. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.