Happy2Play 9780 Posted January 21, 2019 Posted January 21, 2019 It would appear to be a server issue as all custom triggers experience the same issue with the additional zero. So any time set is x10.
Luke 42078 Posted January 21, 2019 Posted January 21, 2019 even a newly configured one? because i just added some logging when the task starts, and the logging is reporting the correct amount of time.
Happy2Play 9780 Posted January 21, 2019 Posted January 21, 2019 even a newly configured one? because i just added some logging when the task starts, and the logging is reporting the correct amount of time. Just looking at the number created, if it is microseconds it is x10 of the time limit actually set. My test was removing one zero so microseconds actually equaled 1 hour not 10 hours. 1
Carlo 4561 Posted January 21, 2019 Posted January 21, 2019 My math says the same thing that 36000000000 microseconds = 10 hours. I think Happy2Play nailed it.
Happy2Play 9780 Posted January 21, 2019 Posted January 21, 2019 No idea what is going on as this test worked properly, deleted and re-added trigger.
Carlo 4561 Posted January 21, 2019 Posted January 21, 2019 No idea what is going on as this test worked properly, deleted and re-added trigger. Emby Twilight Zone??? @@Gilgamesh_48 have you tried creating a new schedule for this task, then deleting the old one? 1
Gilgamesh_48 1240 Posted January 21, 2019 Author Posted January 21, 2019 ...@@Gilgamesh_48 have you tried creating a new schedule for this task, then deleting the old one? Several times.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now