Item allocation failed in Microsoft Dynamics 365 Supply Chain Management

When you see an error below, you will need to check the main source of such issues - Location directives.

Item %Item number% allocation failed.

Shipment %Shipment numebr% has been removed from wave %Wave number%.

No Work was created for Wave %Wave number%.

Solution: 

• If you are using batch enabled product, then ensure location directive has batch enabled and strategy suggested.
• Check location directive and ensure location directive actions are present and valid
• Ensure location directive and directive code is linked well in work template
• Ensure multiple SKU on pick location directive is not checked (it's meant for put type)

The following places can help you identify the root cause:

• Work creation history log
• Processing history in wave

Error: Cloudbuild.Npm.CredentialFetchFailedException: Failed to fetch credentials for feed

I have spent tremendous amount of time figuring out what is going on while installing NPM packages upon new VM deployment for the Supply Chain management. 

An error that I was getting the following:

An error occurred installing your NPM packages. You can set %NPMWRAPPER_LOGLEVEL% to Finest and %NPMWRAPPER_VSTSNPMAUTHEXELOGGINGLEVEL% to Detailed for more detailed logs. Error:
Cloudbuild.Npm.CredentialFetchFailedException: Failed to fetch credentials for feed: 
at Cloudbuild.Npm.Program.<>c__DisplayClass7_0.<<InstallYarnPackagesAsync>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Cloudbuild.Npm.Program.<InstallYarnPackagesAsync>d__7.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Cloudbuild.Npm.Program.Main(String[] args)

Solution: Open Visual Studio 2017 and Sign in. Then re-run init command. 

I am blown away by the simplicity of the solution.

I hope this safe your time!