Facing INCOMPLETE stream status error with MongoDB connection in Airbyte Cloud

Slack Knowledge Base Q&A Connector Questions
, , , ,
1

Summary

Users facing INCOMPLETE stream status error with MongoDB connection in Airbyte Cloud, even after deselecting a table. Seeking input or experiences from others.


Question

Hey there! We are currently using the Airbyte Cloud with the mongoDB connection and are facing some weird breaking errors we can’t make sense of. Is there possibly anyone here who is experiencing something similar right now? Essentially, we’re getting
Some streams either received an INCOMPLETE stream status, or did not receive a stream status at all: <LIST_OF_ALL_STREAMS>
Then we further get

  "internalMessage" : "Missing catalog stream for the stream (namespace: <TABLE_NAME_WE_DESELECTED>, name: <DB_NAME>",
  "externalMessage" : "Something went wrong within the source connector",```
Where we got rid of `TABLE_NAME_WE_DESELECTED` a while ago. We definitely made sure it's deselected in the connection, but it doesn't seem to matter. If anyone has any ideas or experience this before, any input is really welcome :heart:
Thanks!

<br>

---

This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. [Click here](https://airbytehq.slack.com/archives/C021JANJ6TY/p1723620084910319) if you want 
to access the original thread.

[Join the conversation on Slack](https://slack.airbyte.com)

<sub>
["airbyte-cloud", "mongodb-connection", "incomplete-stream-status", "source-connector", "missing-catalog-stream"]
</sub>
2

Hi Robin - I am actually checking on this now with another user. If you still have the Connection available, would you mind checking the state and confirming if TABLE_NAME_WE_DESELECTED is still there?

Connection > Settings > Connection State (drop down at the very bottom of the screen).

3

Hey <@U03AM8G2WHG>! Just checked, and I can’t see it in the connection state. Is there a chance this was an internal bug in the connector? We are currently in the process of migrating to another tool since we didn’t hear back anything from support for a week, couldn’t debug it while having broken production pipelines