Azure Cloud discovery Sensor error: Transaction cancelled: maximum execution time exceededDescription<!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: 5px; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: #cccccc; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size:14px; } ul, ol { margin-left: 0; list-style-position: outside; } --> Symptoms Azure cloud discovery CMPv2 fails with the below error in Ecc queue Sensor error: Transaction cancelled: maximum execution time exceeded Release Any Cause 1) If the data coming back from cloud discovery is huge, it is expected to take time as for the large chunk of data as it had to be processed chunk by chunk. 2) Usually when the data is huge, it is processed by the Discovery Multipage sensors. 3) These multipage sensors would timeout, if the total processing time exceeds the maximum duration configured in the Discovery Multipage sensors Transaction quota rule 4) The default value for maximum duration is 3600s which is 1hr Resolution In order to resolve the issues, perform the steps below : Discovery MultiPage Sensors ================== Navigate to -> System Definition -> Transaction Quota Rules -> Discovery MultiPage Sensors . Change Maximum Duration to 259200 mid.capi.chunk_size ================= Navigate to -> MID Server -> Server -> Select each MID server that you are using for cloud discovery -> Click on "Configuration Parameter" tab -> click "NEW" -> under the Parameter Name section, select "mid.capi.chunk_size" and set the Value to "1000".