Airbyte is an open-source data integration engine that helps you consolidate your data in your data warehouses, lakes and databases.

Airbyte

Captura de Pantalla 2023-10-27 a la(s) 9.07.35.png

Captura de Pantalla 2023-10-27 a la(s) 9.06.28.png

Hi all,
I am having some issues with the new intercom connector. Every time it syncs it takes our to process conversation_parts (which is incremental), I mean last sync for example where 16 hours but only had 1400 records. Any idea how can I fix this?

Sorry <@U05D3AX6R7G>, I'm not sure what you mean. Please try again. :wave:

My intercom connector is taking too long to do a sync, more than 12 hours. And it seems that the fault is of conversation_parts

Hi <@U05D3AX6R7G>, did you manage to solve it? It seems we are facing same problem here.

Hi <@U06AL5SQDD3>, no we haven’t solved it yet, I created an <https://github.com/airbytehq/airbyte/issues/31905|issue> on github but it has not have much movement

I tried migrating to the lastest version 0.3.2 but the issue still happening, if you have any news please LMK

Yes it did not work. Only thing we figured out is that state for parent (conversations) updates when destination is a Postgres (and with postgres destination we do not have the issue) and it does not update on destination GCS.

PG:
```{
    "streamDescriptor": {
      "name": "conversation_parts"
    },
    "streamState": {
      "updated_at": 1703548433,
      "prior_state": {
        "updated_at": 1703548433,
        "conversations": {
          "updated_at": 1697587476
        }
      },
      "conversations": {
        "updated_at": 1697587476,
        "prior_state": {
          "updated_at": 1697587476
        }
      }
    }
  },```


GCS:
```{
    "streamDescriptor": {
      "name": "conversation_parts"
    },
    "streamState": {
      "updated_at": 1703555561,
      "prior_state": {
        "updated_at": 1703555561
      },
      "conversations": {}
    }
  },```


thats a good observation, it makes sense that not updating the state has something to do. I would add this to he github issue if you dont mind

Hi Patricio, to let you know, we downgraded to version 0.1.33 and it is working fine

ohh, thanks for lmk I’ll try it :slightly_smiling_face:

Hey, I'm also running into this issue. How did you downgrade the source version exactly?

Oh you just type over it in the UI. OK. Trying it again now on `0.1.33`

I'm experiencing this issue with 0.6.0. We are on cloud, so no possibility to downgrade, unfortunately. We're syncing to BigQuery and the `conversations_part` takes ages to go from RUNNING to STOPPED state. Even then, it often fails afterwards and we sometimes have 5-10 retries until it manages to finish.. I believe it is unusable, this is a very dissapointing behaviour from a certified source in the cloud..