Yes ... if your package is supposed to start at 6pm you see what package is running before it rolls past 6 and the check again right after the hour ticks over (or wait a minute or two in game time). If it changes to your package ID then you know something other than an AI package could be interfering (example a script).
If it doesn't switch to your package ID you need to find what is stopping your package from triggering.
For example I use conditions a lot and sometimes I have a brain cramp with them where it's my condition stopping the package from starting when that isn't what I intended under the current in game conditions.
You can also examine the vanilla package they're executing before yours to see what conditions or flags it has set (example must complete).
The game parses thru the listed packages from top to bottom each cycle, and if two packages have the same time then the upper one will always execute unless it fails any conditions that are set (then the lower one with the same time gets a chance).
The system that Bethesda provided is powerful when well understood and implemented ... but it's also easy to shoot your own foot (get me to take off my shoes for you some time).