Beast Mode returning greater than 100% for Performance KPI

To keep it as short as possible, I have an On-Time delivery KPI. However, I have to measure on-time/late from two different columns depending on the type of delivery it was. I'm using this beast mode formula to capture those criteria, and then just simply divide it by the total number of deliveries:
(sum(case when `mode`='FTL' and `stop type`='Drop' and `on time / late (2 hrs)`='On Time' and `route category`= 'Transfer' then 1 else 0 end)+sum(case when `mode`='FTL' and `stop type`='Drop' and `on time / late`='On Time' and `route category`<>'Transfer' then 1 else 0 end))/count(case when `mode`='FTL' and `stop type`='Drop' then `route` end)
This formula keeps resulting in % that are over 100%. My first thought was an order of operations, but changing the formula either results in the same answers or something that is less than 1%.
I'll also note that when I take out the count denominator, I get the accurate number of on time deliveries between the two criteria, which makes me believe the denominator or the formula is the issue. Anyone ever have this issue?
Categories
- All Categories
- 2K Product Ideas
- 2K Ideas Exchange
- 1.6K Connect
- 1.3K Connectors
- 308 Workbench
- 7 Cloud Amplifier
- 10 Federated
- 3.8K Transform
- 660 Datasets
- 117 SQL DataFlows
- 2.2K Magic ETL
- 818 Beast Mode
- 3.3K Visualize
- 2.5K Charting
- 84 App Studio
- 46 Variables
- 781 Automate
- 191 Apps
- 483 APIs & Domo Developer
- 84 Workflows
- 23 Code Engine
- 43 AI and Machine Learning
- 22 AI Chat
- 3 AI Projects and Models
- 18 Jupyter Workspaces
- 409 Distribute
- 116 Domo Everywhere
- 282 Scheduled Reports
- 11 Software Integrations
- 146 Manage
- 142 Governance & Security
- 8 Domo Community Gallery
- 49 Product Releases
- 13 Domo University
- 5.4K Community Forums
- 41 Getting Started
- 31 Community Member Introductions
- 115 Community Announcements
- 4.8K Archive