Any error occured when the stage tries to get additional metadata from AMI is not a critical error; so it's better to be output as 'WARN', not 'ERROR'+traceback.
Currently log messages look like these
2021-03-19 14:26:07 (WARN) (ProcessorStage) Failed to process dataset 'mc16_13TeV.346806.MadGraphPythia8EvtGen_A14NNPDF23LO_RS_G_ZZ_llll_c10_m0200.simul.HITS.e7972_e5984_s3126_tid20330292_0
0'
(==) Reason: Non-JSON AMI response: u'AMI#\ncommand : AMIGetPhysicsParamsForDataset\ntime : 2021-03-19 at 02:26:07 PM CET\nresult : \n -> rowset\n#'
2021-03-19 14:25:48 (WARN) (ProcessorStage) Failed to process dataset 'mc16_13TeV.346806.MadGraphPythia8EvtGen_A14NNPDF23LO_RS_G_ZZ_llll_c10_m0200.simul.HITS.e7972_e5984_s3126_tid20330292_0
0'
(==) Reason: Unexpected AMI response: {u'AMIMessage': [{u'executionTime': [{u'$': u'0.0'}], u'error': [{u'$': u'Command not found `AMIGetPhysicsParamsForDatasett`.'}]}]}
2021-03-19 14:25:31 (WARN) (ProcessorStage) Failed to process dataset 'mc16_13TeV.346806.MadGraphPythia8EvtGen_A14NNPDF23LO_RS_G_ZZ_llll_c10_m0200.simul.HITS.e7972_e5984_s3126_tid20330292_0
0'
(==) Reason: No values found in AMI
Any error occured when the stage tries to get additional metadata from AMI is not a critical error; so it's better to be output as 'WARN', not 'ERROR'+traceback.
Currently log messages look like these
Fixes #434