Showing results for 
Search instead for 
Did you mean: 
Regular Visitor

Build fails with exit code 0

Currently, when pcf-scripts build fails, it exits with exit code 0, which is a successful code completion. However, this means that our pipeline build doesn't realize that it has failed, making it harder for us to validate in scenarios such as a PR validation build. Can this be fixed? And is there any workarounds that have been found for this issue?



Super User III
Super User III

You might have more success if you post this question to the PCF section of the forum. Builders with more specialized knowledge of PCF tend to watch that board and answer questions there.

Please Accept as Solution if this post answered your question so others may find it more quickly. If you found this post helpful consider giving it a Thumbs Up.
Community Support
Community Support

Hi @josthom ,

Could you please share a bit more about your issue?

Do you create a PCF control using pcf-scripts command? Could you please share more details about the pcf-scripts that you mentioned?


If you could provide more details about your issue, we could provide a proper workaround for you. In addition, when my PCF project build fails, it would throw error message as below:


rather than return a successful code as you mentioned.


Best regards, 

Community Support Team _ Kris Dai
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

This is how a failure case runs in our Azure Dev Ops build.



Hi @josthom ,

Based on the error screenshot that you mentioned, I think there is something wrong with your project itself.


According to the error message "Cannot find module '@csmsce/msx-platform'", it seems to tell that you do not import/load the '@csmsce/msx-platform' module into your project.

Please check if you have imported/loaded the '@csmsce/msx-platform' module into your project already, if not, please import/load this module into your project firstly, then build your project again, check if the issue is solved.


Best regards,

Community Support Team _ Kris Dai
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

I am not concerned that the build fails, I'm concerned that WHEN it fails, it returns with a successful code, instead of throwing an error, which means our DevOps pipeline can't tell that it fails. We need to be able to tell when it fails so that the PR build can validate PRs.

New Member


We are running into a similar problem at our client. Have you found a resolution to this?

Helpful resources

PA User Group

Welcome to the User Group Public Preview

Check out new user group experience and if you are a leader please create your group

Power Query PA Forum 768x460.png

Check it out!

Did you know that you can visit the Power Query Forum in Power BI and now Power Apps

V3_PVA CAmpaign Carousel.png

Community Challenge - Giveaways!

Participate in the Power Virtual Agents Community Challenge

Carousel 2021 Release Wave 2 Plan 768x460.jpg

2021 Release Wave 2 Plan

Power Platform release plan for the 2021 release wave 2 describes all new features releasing from October 2021 through March 2022.

Top Solution Authors
Top Kudoed Authors
Users online (3,262)