Replicate is only possible if your server time is exactly midnight
You have to clock in (any time before midnight)
Start Activity (exactly at midnight)
End activity (immediately after at midnight)
Generates 24 hours of labor detail
The second piece of code is at the bottom of calculateBurdenhours and calculateLaborhours function
LMAO,
We canāt even explain this problem well enough to you smart people to fully be able to understand that we are running into. How are we supposed to get support to understand?
So the Playdough and crayons didnt work?
Well, they did say they were delicious.
I immediately imagined a stop motion animation with a Lego person clocking in and then out, on a Lego MES
āBut the purple crayon doesnāt taste like grapeā¦ā
Damn Calvin wtf did you do your photo friend #WhoMovedMyCheese #PutITBack made me all twitchy when I saw the name didnāt match the image
People think in terms of good and evil, but really, time is the true enemy of us all. Time kills everything.
Well, lucky for you, I likeā¦ killing time.
Man this is hard to test against. I had MES on test and dev ready to try to do two start/ends on each from 12:00 to 12:01. I got a warning on test so only got two to fire in dev, but neither got 24 hours.
I have had seven of these occur in 2022, so I am going to put my fix in place and monitor.
Yeah itās super hard I had to modify the server time to be able to reliably test it
I created Jira bug ERPS-213225, now it is up to the Product Owner for review and prioritization.
Support says itās intended behavior to give you checks notes 24 hours for 59 seconds of workā¦ that makes sense ā¦ 
I rejected their suggested solution cause itās ā¦ well how do I put this politelyā¦. ITS FREAKING STUPID
This is why we get so angryā¦. Like just accept the damn bug and add it to the backlog donāt give me BS cause you donāt want to deal with it 
Changing the conversation a bit.
As a developer not familiar with the workings of the shop floor, what kind of activities can you be doing that require less than a minute?
How common it is?
Just out of curiosity, to be honest that was my first thought when I opened the thread.
It isnāt common but it should give you 0 not 24 hours
However we do have fast machines that can put out product at a rate of hundreds a minute
I know a different company that makes medical lenses which can do hundreds of serial tracked lenses a minute which each individual unit needs to be tracked and reported on
So it can happen and while I would understand it is uncommon it is definitely a bug to report 24 hours when less than one minute elapsed
I know @jgiese.wci has a machine that counts produced bags as they pass a sensor at the end of the machine and reports again tens or hundreds a minute
@gpayne Here is a replication of it happening, I can make it happen every time under these conditions.
I donāt want to sound confrontational here, but to be honest, the clock in was not really designed to do what you are doing with it.
I agree that their choices were questionable however.
You would be hard pressed to convince me that clocking in/reporting qty/clocking out several times
a minute is a good use of resources, whether itās automated or not.
What possible business reason could there be where you would need costing and timing that accurate?
Couldnāt the whole issue be avoided if the product were reported in batches of x Items every so often and then that divided out ?
If there are valid business reasons to do it this way, I would like to hear that argument.
In manufacturing you can have a bunch of PLCs controlling machines with sensors that can be read through modbus and their values recorded to the operations they are processingā¦ Itās pretty invaluable information for analytics, lot tracing, certifications, etcā¦ We see this a lot with customers in aerospace, or medical equipment manufacturing, pharmaceuticals, etcā¦ A mixing machine might record pH, temperature, reaction vessel pressure, reactant flow rate, error states, etcā¦
Iāve given a few examples before there are things you manufacture that require specific tracking particularly medical devices where you may need to know exactly how long it took who did it and when
However my issue is not that is just simply the fact that they are giving me 24 hours for 1 minute of work and however you slice it thatās a bug. Give me zero and Iāll shut up 
Also this commonly happens as a mistake too, oops I clocks in to the wrong job let me clock out real quick and boom 24 hours
As Hugo said PLCs can report product down to the second or millisecond level.
No, I am in total agreement.
Yes I understand that, and to be clear, I am NOT saying that it is not necessary to collect that data.
What I am saying and asking, is what is gained or lost from reporting every transaction individually, instead of the aggregated data in batches ?
You would obviously still collect the data, but you would report transactions on a less intensive schedule.
