Automated AXIS Model Run Completion Alerts
Every hour, WebRun checks AXIS for batch runs that finished since the last check, reserve valuations, cash flow projections, or stochastic scenario runs, saves the run log to SharePoint, and posts a Microsoft Teams alert naming the run, its duration, and any validation exceptions.
How do I know the moment an AXIS model run finishes?
Every hour, WebRun checks AXIS for batch runs that finished since the last check, reserve valuations, cash flow projections, or stochastic scenarios, and captures each run's duration and validation exception count. It saves the log to SharePoint and posts a Microsoft Teams alert naming the run, so the modeling team knows the moment it is done.
- Long batch runs get a completion alert within the hour instead of manual checking
- Validation exceptions are called out the moment a run finishes, not the next morning
- Every run's log is saved to SharePoint automatically for cycle-over-cycle comparison
Built for actuarial modeling teams · valuation actuaries · actuarial consulting firms · IT support for actuarial systems
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
www.moodysanalytics.comin a real browser with your saved login - no setup, no API keys. -
1
Moody's Analytics AXIS - check for runs that just completed
moodysanalytics.com
WebRun opens Moody's Analytics AXIS to check for runs that just completed. - Open AXIS and check the batch run queue for jobs completed since the last check
- Capture each run's name, product line, duration, and validation exception count
- Note any run that failed or completed with exceptions above your normal threshold
Done when Every run completed since the last check is captured with its status and exception count.
-
2
SharePoint - save the run log
microsoft.com
WebRun opens SharePoint to save the run log. - Open the Model Run Log document library
- Save each completed run's log and exception summary as a dated entry
- Keep a running history so runs can be compared cycle over cycle
Done when The run log library has an entry for every run completed this cycle.
-
3
Microsoft Teams - alert on completion and exceptions
WebRun opens Microsoft Teams to alert on completion and exceptions. - Post the modeling team a completion alert naming the run, its duration, and its exception count
- Flag any run with exceptions above your normal threshold in red
- Link to the saved run log in SharePoint
Done when The modeling team has an alert in Teams for every run that just completed.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it rerun or modify a model if it sees exceptions?
No. WebRun only reads the run's completion status and exception count and reports them. Deciding whether to investigate or rerun a model stays entirely with your modeling team.
How quickly does it notify the team?
It checks AXIS every hour during batch processing, so a completed run gets a Teams alert within the hour instead of someone having to keep checking the queue manually.
What counts as a validation exception?
Whatever your AXIS run flags as an exception: out-of-range results, failed convergence, or a data mismatch, and WebRun reports the count exactly as AXIS records it without reinterpreting the result.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.