Skip to Content
Product Information
Author's profile photo Volker Saggau

HDI: returning multiple deployment errors


Working with SAP HANA Cloud and HDI the tooling stopped at the first error and you had to fix them in the sequence the errors where thrown. All this one by one. This can lead to a lot of cycles that are time consuming and do not support the workflow one had in mind.


With SAP HANA Cloud March 2022 the HDI can now return the first error it can detect per each “dependency branch”.

In this schematic tree we would see 3 errors caused in various depths in the tree.

The HDI works through the individual branches until finished or with error message.

How can you activate this behaviour?

Today do get this behaviour by default in the Business Application Studio environment. We are setting the parameter to false and you can not even overwrite this anymore!



Adding stop_on_error parameter is not needed anymore



Two error caused by wrong syntax

As you can see in the sample the errors are reflected in Business Application Studio (BAS) with 2 highlighted HDBTABLE definitions.



The HDI parameter “stop on error” is now set by default to false and can not be overwritten in BAS. It allows the developer to reduce the cycle times with HDI and allow to find faster and easier typos or other errors within the design time objects.


Here a view to the help document:

Stop_on_error%20documentationYou may be interested in the other parameters as well.

Stop_on_error documentation

Current version: Q2/2023


Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Michael Cocquerel
      Michael Cocquerel

      Will it be available on premise at some time ?

      Author's profile photo Volker Saggau
      Volker Saggau
      Blog Post Author

      Hi Michael,

      Indeed we plan to bring this to HANA on premise as well. Current planing is for SP7. The Roadmap is the official information. I am working to get it into the list.



      Author's profile photo Ruben Ramirez
      Ruben Ramirez

      Hi Volker,

      i'm getting this error with stop_on_error:

      " Error: "stop_on_error": the parameter key is unknown; valid parameter keys are [container_lock_wait_timeout, enable_make_enforcer, max_parallel_jobs, optimized_redeploy, simulate_make, skip_unchanged_expansions, stop_after_graph_creation, stop_after_make, trace_context, trace_level.*, treat_warnings_as_errors, undeploy_dependent_recursively, use_redeploy_for_unchanged_content, validate_virtual_tables, work_items_graph_prefetch_limit, work_items_queue_combine_limit] [8214236]"

      Do you have a solution for it?

      Best Regards


      Author's profile photo Volker Saggau
      Volker Saggau
      Blog Post Author

      Hi Ruben,

      I changed the text. It is no longer needed to add this in BAS.

      However if you still encounter issues, please open a ticket.