That was one concern for our use case, but that was mainly driven by strict aws lambda execution timeouts, which airbyte does not have. Another is that some entities of a source, e.g. individual projects from a Jira source, have insufficient permission configurations or other misconfigurations that we don’t want to our jira connection to fail on, i.e. the connection should log the error and keep running as normal.