Forum Discussion
Save button not working for Data Pipeline
Hallo Team,
Currently, I am experiencing that even after making modifications in the data pipeline and saving it (getting a successfully saved message), the pipeline is not updated and runs the previous version...
The 'save as' button got this error message: {"message":"Request failed with 400(Bad Request): {\"error\":{\"code\":\"BadRequest\",\"pbi.error\":{\"code\":\"BadRequest\",\"exceptionCulprit\":1}}}, \nrequestid: aeeae4e7-7e6a-2ee7-ff8e-a6d31a9b067f"}
Do you know about it?
Hi tapapp,
Thanks for reaching out microsoft community support.
please try following below troubleshooting steps to address the issues you're facing:
- Verify Changes Are Saved
- After saving the pipeline, refresh the page or log out and log back in to ensure changes are reflected. If the pipeline keeps running the older version, manually stop it and restart it to apply the updated configuration. Ensure there are no dependent tasks or jobs locking the pipeline.
- Test "Save As"
- Simplify and Save: Try saving a simpler version of the pipeline to isolate the issue. When using "Save As," ensure the new name does not conflict with an existing pipeline. Test the operation in another browser or an incognito/private browsing session.
- Check Logs in Fabric:
- Go to Settings or the Monitor section of the Fabric workspace. Look for logs related to the error or failed request using the requestid. Ensure all inputs, outputs, and transformations are correctly configured.
- Clear Cache and Reset
- Clear your browser cache and cookies, Restart the browser and log back into Microsoft Fabric. If using Power BI Desktop or other tools in conjunction, ensure they’re updated.
- Test a New Pipeline
- Create a new pipeline as a test. Copy parts of the existing pipeline incrementally to see if any specific element is causing the issue.
please refer to similar community forum thread: Solved: Re: "Save as" button not working for pipelines - Microsoft Fabric Community
Thanks,
Prashanth Are
MS Fabric community support.
Did I answer your question? Mark my post as a solution, this will help others!
If my response(s) assisted you in any way, don't forget to drop me a "Kudos"
- Verify Changes Are Saved
4 Replies
- NandanHegdeSuper User
Is the validation succesful before you are trying to Save the pipeline?
- tapappNew Member
Yes, the validation was also successful.
- v-prasareCommunity Support
Hi tapapp,
Thanks for reaching out microsoft community support.
please try following below troubleshooting steps to address the issues you're facing:
- Verify Changes Are Saved
- After saving the pipeline, refresh the page or log out and log back in to ensure changes are reflected. If the pipeline keeps running the older version, manually stop it and restart it to apply the updated configuration. Ensure there are no dependent tasks or jobs locking the pipeline.
- Test "Save As"
- Simplify and Save: Try saving a simpler version of the pipeline to isolate the issue. When using "Save As," ensure the new name does not conflict with an existing pipeline. Test the operation in another browser or an incognito/private browsing session.
- Check Logs in Fabric:
- Go to Settings or the Monitor section of the Fabric workspace. Look for logs related to the error or failed request using the requestid. Ensure all inputs, outputs, and transformations are correctly configured.
- Clear Cache and Reset
- Clear your browser cache and cookies, Restart the browser and log back into Microsoft Fabric. If using Power BI Desktop or other tools in conjunction, ensure they’re updated.
- Test a New Pipeline
- Create a new pipeline as a test. Copy parts of the existing pipeline incrementally to see if any specific element is causing the issue.
please refer to similar community forum thread: Solved: Re: "Save as" button not working for pipelines - Microsoft Fabric Community
Thanks,
Prashanth Are
MS Fabric community support.
Did I answer your question? Mark my post as a solution, this will help others!
If my response(s) assisted you in any way, don't forget to drop me a "Kudos"
- Verify Changes Are Saved
- eugmeidAdvocate I
In case it is helpful to future searchers, I ran into a similar issue and it was caused by a deactivated activity having invalid parameters. Depsite the issue, validating the pipeline didn't raise any problems.