Different Schedule UI in Data Pipeline

[CCal]

Hi, 

I noticed a difference in UI when it comes to the schedule screen of a data pipeline.

One Pipeline is created in July and the other one is today (sept).

As you can see, the older pipeline schedule offer the next refresh time.
Anybody knows why there's a difference?

Both pipelines has notebooks activities in it.

[AntoineW · Accepted solution]

Hello @CCal, 

Thanks for the question ! 

The difference you're seeing in the schedule screen UI between your July and September pipelines is likely due to the recent update in Microsoft Fabric that introduced Multiple Scheduler support (August 2025).

Pipelines created before this update use the older UI, which may show the “Next Refresh Time” more directly. Pipelines created after the update use the new UI, which is designed to support multiple schedulers per item — but currently only displays the default job type in the UI.

Microsoft is progressively rolling out full UI support for all scheduler types, so this behavior is expected and should stabilize soon. You can still manage all schedulers via the API or Git integration.

Hope it can help you ! 

Best regards,

Antoine

[CCal]

Hi @tayloramy , 

Both Pipelines are in the same workspace. 

I did some more testing in other workspaces, I get the same "new" UI. (by the minute, hourly, daily, etc)

Interestingly, when I edited an older pipeline with the "old" UI, the UI changes into the "new" one.

Is there a feature change rolling out or did I miss a announcement about this?

[tayloramy]

Hi @CCal, 

I think this might have something to do with the multi schedule feature that was rolled out last month. 

Unlocking Flexibility in Fabric: Introducing Multiple Scheduler and CI/CD Support | Microsoft Fabric...

Looks like this is expected. 

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, please mark this as the solution.

[tayloramy]

Hi @CCal, 

I just made a test pipeline in my workspace, and I am able to see the next refresh date: 

Have you noticed this being consistent with all new pipelines you make, or is it this specific one that's giving the wonky UI behaviour? 

Are both pipelines in the same workspace? 

If you found this helpful, consider giving some Kudos.
If I answered your question or solved your problem, mark this post as the solution.