Is anyboyd else having issues where the normalization completes successfully, but the job itself is marked as failed? I know this isn’t the place for troubleshooting, but I have posted on the discourse forum, and not got a reply. The help from the airbyte team itself is seemingly non-existent. I’ve tried upgrading to the latest verison of airbyte itself and connectors. destination is snowflake - issue is happenign with github, jira and zendesk all the same.

If the source or destination connectors are encountering errors, they may exit with an error code > 0 This would mark the job sync as failed at the end. Regardless of an error during the first phase of replication (the EL phase), normalization is still ran afterward to try normalize whatever still managed to be transferred. So it's possible, it might complete successfully without errors

@Garrett McClintock is it this the topic you posted in Discourse? https://discuss.airbyte.io/t/initial-syncs-run-subsequent-all-fail-github-and-jira/1030/3

@Marcos Marx (Airbyte) yes it is

@Garrett McClintock did you check my comments? Github server threw 502 error, did you try again? For Jira the problem is related to custom fields created in project level doesn’t have context infotmation

@Marcos Marx (Airbyte) - I just saw that, thanks. I will break that out into separate tickets - it looks like GitHub was just hitting an API limit (but couldn’t find that in the log - I must’ve missed that). Re: JIRA, are custom fields not supported?

They are, but there are custom fields created in project levels that aren't supported. Check the issue I posted in /Discourse topic

Ty