

Look at the output and find which module is failing. You’ll usually see the module itself fail(doing a push) or the full deploy will retry starting the module 3 times before giving up. This can happen with full deploys where the entire project is zipped up, or partial “push” deploys of single NodeJS modules(Including the app-router, and HDI DB modules which are themselves specialized NodeJS apps). If you’re deploying an Multi-Target Application(MTA) to SAP Cloud Platform Cloud Foundry, you may find that it can fail if there is a mismatch in the files your sending as part of your project and the system’s attempt to pull in additional dependent files during the deployment. If you use NodeJS for anything in your project(and it’s hard not to) you may find yourself stuck in EINTEGRITY hell.
