@erictgrubaugh i think i saw that before, and it was due to the workflow being in an open / active state on a record perhaps?