Forum Discussion
Eventstream shows data in preview but the connected destinations are not showing that data at all
What am I doing wrong here ? or is it just a waiting game ? I dont think 1 row of data would take that long. In the screenshot you can only see the headers and not the data underneath for privacy reasons.
Hi ahmedmc ,
I had exactly the same issue, but not during initial setup — this happened with a pipeline that had been running smoothly for several months.
One day data simply stopped arriving at the destination. No error in Fabric, no warnings on the canvas, nothing. The preview kept showing data correctly, which made it even more confusing because everything *looked* fine.
What worked for me: manually resending messages to the source. As soon as I did that, the destination started processing again on its own.
It's a very silent and hard-to-detect behavior: the pipeline gets "frozen" somewhere internally without Fabric surfacing it as an error. Most likely there's some kind of internal disconnection between the stream and the destination connector that doesn't auto-recover.
The underlying issue — which I have pending to submit as a product idea to Microsoft — is that there is no rerun or force-reprocess mechanism. If the pipeline falls into this state, you have no way to trigger it from the UI without having to manually resend data.
My suggestion: try manually resending a few messages to your source and see if the destination reactivates. If your case is like mine, it should work.
Let us know how it goes — it could be really useful for others hitting the same issue.
If this was helpful, please mark it as a solution and give it a 👍 to help others in the community. Thanks!
5 Replies
- arabalca
Super User
Hi ahmedmc ,
I had exactly the same issue, but not during initial setup — this happened with a pipeline that had been running smoothly for several months.
One day data simply stopped arriving at the destination. No error in Fabric, no warnings on the canvas, nothing. The preview kept showing data correctly, which made it even more confusing because everything *looked* fine.
What worked for me: manually resending messages to the source. As soon as I did that, the destination started processing again on its own.
It's a very silent and hard-to-detect behavior: the pipeline gets "frozen" somewhere internally without Fabric surfacing it as an error. Most likely there's some kind of internal disconnection between the stream and the destination connector that doesn't auto-recover.
The underlying issue — which I have pending to submit as a product idea to Microsoft — is that there is no rerun or force-reprocess mechanism. If the pipeline falls into this state, you have no way to trigger it from the UI without having to manually resend data.
My suggestion: try manually resending a few messages to your source and see if the destination reactivates. If your case is like mine, it should work.
Let us know how it goes — it could be really useful for others hitting the same issue.
If this was helpful, please mark it as a solution and give it a 👍 to help others in the community. Thanks!
I think the problem was that if destination is not connected and data was pushed, it will show in preview and might give the illusion as if its queued up to be sent the moment a destination is connected. Only the data that was pushed after connecting the destination goes through.
v-hashadapuCommunity Support
Hi ahmedmc , Thank you for the update. We're glad to hear the issue has been resolved.
If you have any more questions, please feel free to create a new post. We're always happy to help.
- deborshi_nag
Hello ahmedmc have you published the eventstream? Try to refresh the destination LH and the EV and see if that works.
- v-hashadapu
Hi ahmedmc , Hope you are doing well. Kindly let us know if the issue has been resolved or if further assistance is needed. Your input could be helpful to others in the community.
