All templates

Automated CensiTrac Failed Cycle Alerts

Every few minutes, WebRun checks Censis for any sterilizer cycle marked failed, whether on a chemical integrator, a physical parameter, or a biological indicator, lists every tray in that load, posts the hold to your SPD Teams channel, and texts the on-call supervisor through Twilio so no failed load reaches a case by mistake.

Deploy this workflow Browse all templates
Runs on WebRun · Strict Lockdown policy
Checks every 10 minutes, day and night WebRunorchestrates each step
1 Censis flag failed sterilization cycles
2 Microsoft Teams post the hold and tray list
3 Twilio text the on-call supervisor
In short

How do I get notified immediately when a sterilization cycle fails?

WebRun watches Censis for any sterilizer cycle that fails its integrator, physical parameters, or biological indicator, and immediately lists every tray in that load. It posts the hold to your SPD Teams channel and texts the on-call supervisor through Twilio, so a failed load gets caught and reprocessed before it ever reaches a case.

  • Failed loads are held and flagged within minutes, day or night
  • On-call supervisors get texted instead of finding out at case time
  • Every tray in a failed load is listed, not just the sterilizer number

Built for Sterile processing technicians · SPD supervisors · infection prevention teams · perioperative leaders

Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order - in plain language, so you can adjust anything.

  1. WebRun signs in and gets to work

    Opens portal.censis.com in a real browser with your saved login - no setup, no API keys.

  2. 1
    Censis - flag failed sterilization cycles
    censis.com
    WebRun in Censis: flag failed sterilization cycles
    WebRun opens Censis to flag failed sterilization cycles.
    • Open Censis (CensiTrac) and check for any sterilizer load marked Failed on its cycle record
    • List every tray and set included in that load
    • Confirm the load's quarantine hold is set so nothing in it can be released

    Done when Every failed load this run has its trays listed and its hold confirmed.

  3. 2
    Microsoft Teams - post the hold and tray list
    microsoft.com
    WebRun in Microsoft Teams: post the hold and tray list
    WebRun opens Microsoft Teams to post the hold and tray list.
    • Post the failed load, the sterilizer number, and the full tray list to the SPD channel
    • State plainly that the load is on hold pending reprocessing
    • Note the failure type: chemical integrator, physical parameter, or biological indicator

    Done when The SPD team can see exactly which trays are held and why.

  4. 3
    Twilio - text the on-call supervisor
    twilio.com
    WebRun in Twilio: text the on-call supervisor
    WebRun opens Twilio to text the on-call supervisor.
    • Send a short text to the on-call SPD supervisor's number with the sterilizer number and tray count
    • Include a link back to the full Teams post
    • Only send once per failed load, not once per tray

    Done when The on-call supervisor has been texted about the failed load.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
portal.censis.com
ScheduleRuns automatically on this cadence
Checks every 10 minutes, day and night
DeliveryHow each run's result reaches you
Failed-cycle hold · Twilio SMS
OutputWhat each run produces - A held-load notice per failed cycle, the full tray list, and a text to the on-call supervisor.
Alert
Setup & safety

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.

Your credentials stay in your own private environment - WebRun never stores your passwords.
Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST
Typed input ALLOW
Shell command BLOCK
File uploads BLOCK
Runs in a contained environment More on policies
Good to know

Questions, answered

Will it release the trays once the cycle is corrected?

No. WebRun only flags the hold and notifies your team. Releasing a tray after reprocessing and a passed check is always a decision your SPD lead makes.

Does it text for every single tray in a failed load?

No, just one text per failed load listing the sterilizer and how many trays are affected, with the full breakdown posted to Teams so the phone alert stays short.

What counts as a failed cycle?

Any load Censis marks failed on a chemical integrator, a physical parameter like temperature or pressure, or a biological indicator, whichever your sterilizers record.

Keep going

Related templates

Automated CensiTrac BI Test Result Tracking
WebRun checks Censis for biological indicator readouts as they post, logs every result to a Google Sheet by sterilizer and load, and texts your SPD lead through Twilio the moment any BI comes back positive so the load gets held.
Censis›Google Sheets›Twilio
Automated CensiTrac Count Sheet Reconciliation
WebRun checks Censis for any tray where the physical count did not match its count sheet, posts a Teams alert naming the exact discrepancy, and logs it to a Google Sheet so your quality team can spot patterns by tray type or shift.
Censis›Google Sheets›Microsoft Teams
Automated CensiTrac Daily Throughput Digest
Every night, WebRun tallies how many trays moved through decontamination, assembly, and sterilization in Censis, logs the count and turnaround time to a Google Sheet, and posts your manager a Teams digest highlighting the slowest stage of the day.
Censis›Google Sheets›Microsoft Teams

Put this on autopilot.

Turn it on in minutes - or have our team set it up for you.

Deploy this workflow Talk to us