<@U04SE163WC8> I added two streams on a hubspot co...
# ask-ai
m
@kapa.ai I added two streams on a hubspot conection and airbyte says it is “queued for next sync” but when the sync comes, nothing happen
u
Based on the information provided in the knowledge sources, I can offer some insights into your situation with the HubSpot connection in Airbyte. The "Queued for next sync" status you're seeing is a normal part of Airbyte's sync process. According to the [Review the stream status](https://docs.airbyte.com/cloud/managing-airbyte-cloud/review-connection-status#review-the-stream-status) documentation, this status means that "The stream has not synced yet, and is scheduled to be synced in the next scheduled sync." However, if nothing happens during the next sync, there could be a few reasons for this: 1. Permissions: HubSpot requires specific permissions for different streams. As mentioned in the [HubSpot troubleshooting guide](https://docs.airbyte.com/integrations/sources/hubspot#troubleshooting), some streams need to be enabled before they can be read, especially when using API Key authentication. Make sure you have the necessary permissions for the streams you've added. 2. Scopes: HubSpot uses scopes for each API call, and each stream is tied to a scope. Review the [HubSpot OAuth scope documentation](https://developers.hubspot.com/docs/api/working-with-oauth#scopes) to ensure you have the correct scopes for the streams you're trying to sync. 3. No new data: If there's no new data in the source since the last sync, Airbyte might not show any changes. As mentioned in the [incremental data synchronization tutorial](https://airbyte.com/tutorials/incremental-data-synchronization#step-7), "If a sync is executed without making any modifications on the source database, no records will be emitted, and no changes will be made on the destination database." To troubleshoot this issue: 1. Check the logs for any error messages or warnings. 2. Verify that you have the necessary permissions and scopes for the streams you've added. 3. Ensure there's new data in the source since the last sync. 4. If the problem persists, you might want to try refreshing the source schema. As mentioned in the [HubSpot migration guide](https://docs.airbyte.com/integrations/sources/linkedin-ads-migrations#migration-steps-1), you can go to the schema tab of your connection and click "refresh source schema" to pull in new streams for syncing. If these steps don't resolve the issue, you may need to reach out to Airbyte support for further assistance.
m
@kapa.ai ok thanks i will double check. I dont have any error on airbyte when sync though. it is like the sync didnt start for these streams
u
A message from kapa.ai
u
If the sync doesn't seem to start for these streams, it could be due to a few reasons: 1. Stream Selection: Ensure that the streams are selected for sync in your connection settings. You can verify this by going to the connection settings in Airbyte and checking if the streams are selected. 2. Data Availability: If there's no new data in the streams since the last sync, Airbyte might not show any changes. 3. Permissions and Scopes: As mentioned earlier, HubSpot requires specific permissions for different streams. Some streams need to be enabled before they can be read. Also, each stream is tied to a scope and will need access to that scope to sync data. If you've checked all of these and the issue persists, it might be helpful to isolate the issue by creating a separate connection with just these streams and see if the sync works. This was suggested in a [forum post](https://discuss.airbyte.io/t/2049) discussing a similar issue. If none of these suggestions help, it would be best to reach out to Airbyte support or post in the Airbyte community forum for further assistance.
t
hey @Martin Lainez! I have the exact same issue... Did u find a fix by any chance ?
m
Hello Tom, the error was due to an error on hubspot side : the scope wasnt open for these new streams
t
Hey ! Thanks a lot that was the issue ! By any chance do you know the scopes to add for the
ticket_pipelines
stream ? Can't find the information on the doc 😩