Forum Discussion

AkshaykumarK's avatar
AkshaykumarK
New Member
1 year ago
Solved

Reflex 500 Error in One Activator

I'm using Microsoft Fabric Eventstream with the Sample Yellow Taxi dataset as input. The stream outputs to three destinations: a KQL database, Activator 1, and Activator 2. All three receive the same data. While Activator 1 works without issues, Activator 2 shows a runtime log error saying: There is a problem outputting to Reflex. Failed to send data to Reflex.  Both activators are configured similarly.

I’m not sure why only Activator 2 is logging this error while Activator 1 does not. Could this be related to the CloudEvent format, or is it a Reflex-side issue? Any guidance on how to fix or debug this would be appreciated.

Activator
  • svelde's avatar
    svelde
    1 year ago

    Hello AkshaykumarK,

    welcome to this community forum.

     

    A 500 error probably indicates something went wrong in the backend (server side error).

     

    Then, the issue has a technical source, and is probalby not triggered by yourdata itself. 

     

    Normally, administrators (like those administering the Fabric backend) are notified and will take actions on this level of challenges.

     

    Can you check to see this issue still remains?

     

    if so, provide feedback in the portal itself (via the feedback icon in the right upper corner in the Fabric portal):

     

    And yes, this will be picked up by the product teams.

4 Replies

  • svelde's avatar
    svelde
    Super User
    1 year ago

    Hello AkshaykumarK,

    welcome to this community forum.

     

    A 500 error probably indicates something went wrong in the backend (server side error).

     

    Then, the issue has a technical source, and is probalby not triggered by yourdata itself. 

     

    Normally, administrators (like those administering the Fabric backend) are notified and will take actions on this level of challenges.

     

    Can you check to see this issue still remains?

     

    if so, provide feedback in the portal itself (via the feedback icon in the right upper corner in the Fabric portal):

     

    And yes, this will be picked up by the product teams.

  • v-nmadadi-msft's avatar
    v-nmadadi-msft
    Community Support
    1 year ago

    Hi AkshaykumarK 

    I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.


    Thank you.

  • v-nmadadi-msft's avatar
    v-nmadadi-msft
    Community Support
    1 year ago

    Hi AkshaykumarK 

    May I check if this issue has been resolved? If not, Please feel free to contact us if you have any further questions.


    Thank you

  • v-nmadadi-msft's avatar
    v-nmadadi-msft
    Community Support
    11 months ago

    Hi AkshaykumarK ,

    As we haven’t heard back from you, we wanted to kindly follow up to check if the suggestions  provided by the community members for the issue worked. Please feel free to contact us if you have any further questions.

     

    Thanks and regards