PedroHMCosme d265e3328c fix(simple_metrics): fail the run explicitly when the adaptive state update fails (SIENTIAPDE-2191) ...

Drop the try/except around update_simple_metrics_adaptive_state in the workflow and the broad except in the activity, so Mongo failures fail the run and show up in the Temporal metrics (PR #59 review). Invalid frequency_alert stays a warning + skip (the orchestrator ignores it too) and a malformed adaptive_state is read as not escalated.

2026-10-08 17:45:44 -03:00

..

__init__.py

SIENTIAPDE-1084

2025-09-01 16:03:03 -03:00

activities.py

feature-rc/SIENTIAPDE-2164 - refactor: centralize prediction metadata write in a dedicated activity; REPEAT now writes metadata too

2026-10-01 17:46:20 +02:00

api.py

SIENTIAPDE-1646

2026-05-07 17:02:25 -03:00

gates.py

feature-rc/SIENTIAPDE-2164 - refactor: centralize prediction metadata write in a dedicated activity; REPEAT now writes metadata too

2026-10-01 17:46:20 +02:00

mlflow.py

SIENTIAPDE-1646

2026-09-25 12:45:19 -03:00

model_metrics.py

fix(simple_metrics): fail the run explicitly when the adaptive state update fails (SIENTIAPDE-2191)

2026-10-08 17:45:44 -03:00

opc.py

QTZPOC-20

2026-09-10 14:15:42 -03:00

prediction_metadata.py

feature-rc/SIENTIAPDE-2164 - refactor: centralize prediction metadata write in a dedicated activity; REPEAT now writes metadata too

2026-10-01 17:46:20 +02:00

storage.py

rc/SIENTIAPDE-2173- refactor: move repeat_last_prediction from sientia-dataops-library into Storage, add metadata_id

2026-10-02 18:41:18 +02:00