QUESTION/ISSUE Error 400: "KeyError: 'IncidentTriggered" on multiple modules

[zjb1003]

Hello.

I am getting an error 400 on multiple STAT modules every time STAT runs, always pointing back to KeyError: 'IncidentTriggered. We upgraded to 2.3.0 back in January of this year, however, I am not sure if this problem started before or after the version upgrade.

Here is the output for User Exposure Module as an example:

{
"statusCode": 400,
"headers": {
"Transfer-Encoding": "chunked",
"Date": "Tue, 14 Apr 2026 13:06:40 GMT",
"Content-Type": "application/json",
"Content-Length": "1042"
},
"body": {
"Error": "Module processing failed, an unknown exception has occurred.",
"InvocationId": "Redacted",
"STATVersion": "2.3.0",
"Traceback": [
"Traceback (most recent call last):\n",
" File "/home/site/wwwroot/modules/init.py", line 19, in main\n return_data = coordinator.initiate_module(module_name=module_name, req_body=req_body)\n ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n",
" File "/home/site/wwwroot/shared/coordinator.py", line 25, in initiate_module\n return_data = file.execute_file_module(req_body)\n ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n",
" File "/home/site/wwwroot/modules/file.py", line 15, in execute_file_module\n base_object.load_from_input(req_body['BaseModuleBody'])\n",
" File "/home/site/wwwroot/classes/init.py", line 171, in load_from_input\n self.IncidentTriggered = basebody['IncidentTriggered']\n ~~~~~~~~^^^^^^^^^^^^^^^^^^^^^\n",
"KeyError: 'IncidentTriggered'\n"
]
}
}

The input for all modules in the Base Module Body:

Here are the modules which consistently fail (I have not been able to find any successes for these modules in the run history):

Here are the modules which consistently succeed (Rarely ever seen them fail):

[briandelmsft]

@zjb1003 verify what is being passed to the failing modules as the Base Module Body is in fact the dynamic value 'Base Module Body' and nothing else. There isn't a path where a legitimate Base Module Body would be missing the key IncidentTriggered as it it starts in a default state of false when the base module creates a instance of the class and will later potentially change True if the base module determines it was trigger by an incident and not an alert.... but it should never be missing. If you don't see a problem when looking at the inputs to one of the failing modules, please send me a redacted version of the inputs to a run, and a screenshot of the module inputs when in edit mode on the logic app