Forum Discussion
Cannot Edit Pipeline Schedule
- 2 years ago
Hi wjbreitenbach you will need to specify an End date and time for the Apply button to become active and allow you to apply the changes.
Thanks for using Fabric Community.
As I understand that you are trying to add time to an existing data pipeline schedule but the apply button is not enabled to do the required changes.
When I tried to repro the same scenario, I am not getting any issue with the apply button. You can view or edit the schedule again at anytime by selecting the Schedule button again. For more details please refer : Scheduled data pipeline runs
Please find the screen shorts for reference.
Here I have scheduled for every 5 mins.
Here I have changed the schedule time to every 10 mins and able to see Apply button enabled.
Here are some troubleshooting steps that might help you.
- Try clearing the cache of your browser. Sometimes, a corrupted cache can cause problems.
- If you are still having problems, try using a different browser to access data pipeline.
I hope this information is helpful. Please do let us know if you have any further questions.
- wjbreitenbach2 years agoFrequent Visitor
I cleared the cache and also used Chrome instead of Edge. I still am not able to apply the changes to my schedule. I have 2 other data pipeline schedules and cannot edit any of them. Do you have any other troubleshooting tips?
- AndyDDC2 years agoMost Valuable Professional
Hi wjbreitenbach you will need to specify an End date and time for the Apply button to become active and allow you to apply the changes.
- wjbreitenbach2 years agoFrequent Visitor
Thank you AndyDDC ! Setting an End Date enabled the Apply button. I will just have to remember to extend the date when it is ready to expire since it seems you cannot have an open-ended schedule.
- v-cboorla-msft2 years agoMicrosoft Employee
- antik1 year agoFrequent Visitor
Just noticed this myself as I'm building our first production application on Fabric data pipelines. The requirement to always fill an end date does not seem like the most robust solution for long term production use cases. Am I missing a point here - is there a reason why the end date is required or is this something MS should reconsider?