Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Enhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.

Reply
Anonymous
Not applicable

Configuration for action to occur (timing question)

Hi,

 

I am using Activator and Reflex to monitor messages coming in from EventHub.

 

The message comes in and I can see it received in Activator and then Reflex as a destination.

 

The action is to call a pipeline which Reflex does.

 

Thing is it can take 4-8 minutes for Reflex to actually execute the action and call the pipeline and its under no load.

 

Is that configurable somewhere?  I would think it should be close to real-time to trigger the action.

 

Thanks!

1 ACCEPTED SOLUTION
Anonymous
Not applicable

Hi @Anonymous ,

In general, Reflex itself will have some latency due to the size of the data and the complexity of the object. I created a Reflex myself (using a simple data source and no other transformations), and there was a delay of about 2-3 minutes between the time the condition is met and the trigger being triggered. This delay is unavoidable.
Solved: Latency between trigger activation and alert - Microsoft Fabric Community

Also you mentioned that you used pipeline, I'm not sure what steps you placed in your pipeline besides Reflex. But the pipeline itself will start running with a slight delay, and it will also take some time for the pipeline to run successfully from start to finish, depending on the amount of data you have, the complexity of the conversion operation you are doing, and the number of steps in the pipeline.

vjunyantmsft_0-1723174257412.png


If you want to reduce wait times, try optimizing your data model to reduce the amount of data and simplify the conversion operations to try to reduce these delays.

Best Regards,
Dino Tao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

View solution in original post

2 REPLIES 2
Anonymous
Not applicable

Hi @Anonymous ,

In general, Reflex itself will have some latency due to the size of the data and the complexity of the object. I created a Reflex myself (using a simple data source and no other transformations), and there was a delay of about 2-3 minutes between the time the condition is met and the trigger being triggered. This delay is unavoidable.
Solved: Latency between trigger activation and alert - Microsoft Fabric Community

Also you mentioned that you used pipeline, I'm not sure what steps you placed in your pipeline besides Reflex. But the pipeline itself will start running with a slight delay, and it will also take some time for the pipeline to run successfully from start to finish, depending on the amount of data you have, the complexity of the conversion operation you are doing, and the number of steps in the pipeline.

vjunyantmsft_0-1723174257412.png


If you want to reduce wait times, try optimizing your data model to reduce the amount of data and simplify the conversion operations to try to reduce these delays.

Best Regards,
Dino Tao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Anonymous
Not applicable

It looks like it's polling for sure.. It picked up two I sent ~4-5 minutes apart at the same time from the looks of it.. 

1. I would like to be able to control the pool interval time.

2. Is there a way to control collisions?  Let's say if both pieplines run at the same time, it causes me issues (which it does).

Thanks!

 

pufferb_0-1723134641118.png

 

 

Helpful resources

Announcements
Fabric July 2025 Monthly Update Carousel

Fabric Monthly Update - July 2025

Check out the July 2025 Fabric update to learn about new features.

August 2025 community update carousel

Fabric Community Update - August 2025

Find out what's new and trending in the Fabric community.

Top Kudoed Authors