Using Airbyte OSS k8s (0.63.8) and helm my Salesforce syncs have not been working properly. Error I'm seeing in the status section is:

Warning from destination: Some streams were unsuccessful due to a source error: [io.airbyte.protocol.models.v0.StreamDescriptor@6eed46e9[name=TaskWhoRelation,namespace=sfdc,additionalProperties={}], io.airbyte.protocol.models.v0.StreamDescriptor@4d20616a[name=TSPC__EventGroup__Feed,namespace=sfdc,additionalProperties={}],

Based on the information provided in the knowledge sources, it appears that you're experiencing an issue similar to what has been reported in other Airbyte versions. While the exact version you're using (0.63.8) is not specifically mentioned in the provided documents, there are some relevant insights that might help explain the problem you're encountering. The error message you're seeing is similar to those reported in other issues, where certain streams are unsuccessful due to a source error. This type of error has been observed in various Airbyte versions and with different connectors. A possible explanation for this issue comes from [Github Issue #45157](https://github.com/airbytehq/airbyte/issues/45157), which describes a problem where random "A stream status has been detected for a stream not present in the catalog" errors cause multiple retries and eventually succeed. While this isn't exactly the same error you're seeing, it suggests that there might be an issue with stream status detection or catalog synchronization. Another relevant piece of information comes from [Github Issue #40555](https://github.com/airbytehq/airbyte/issues/40555), where users experienced similar issues with stream errors after upgrading to newer versions of Airbyte. In some cases, downgrading the connector version resolved the issue. Given this information, you might want to try the following: 1. Check if there's a more recent version of the Salesforce source connector available and try upgrading it. 2. If upgrading doesn't help, you could try downgrading the Salesforce source connector to an earlier version that you know worked correctly. 3. Verify that your Salesforce source configuration is correct and that you have the necessary permissions to access all the streams you're trying to sync. 4. Review the full logs of your sync job to see if there are any more specific error messages that might provide additional clues about the root cause of the issue. If these steps don't resolve the issue, you may want to consider opening a new issue on the Airbyte GitHub repository, providing detailed information about your setup, the full error logs, and the steps you've taken to troubleshoot the problem. It's worth noting that the knowledge sources don't provide a definitive solution for your specific case with Salesforce on Airbyte OSS 0.63.8 using Helm on Kubernetes. The issue might require further investigation by the Airbyte team.