Hi Chuck,
My first suspicion would be loops in the supply chain – where the same material is both being consumed and produced by operations in the same supply path.
In this case you should still see continuing CPU utilization of the frepple planning engine.
If the planning engine crashed and died, then it’s a bug where some bad input data condition isn’t handled robustly.
You can file a case on our portal if you want us to look into it.
Regards,
Johan De Taeye
Mob: +32 477.385.362
Skype: jdetaeye
Visit us at https://frepple.com
* * * * * * * TECHNICAL DATA (ITAR) WARNING * * * * * * *
SilencerCo, LLC manufactures a variety of defense components within the meaning of the (ITAR) INTERNATIONAL TRAFFIC IN ARMS REGULATION (22 CFR Ch 1 >Sub M > Part 120 >Section 120.6). As such, this e-mail and any attachments may include technical data subject to the U.S. ARMS EXPORT CONTROL ACT (22 U.S.C. Section 2751), U.S. EXPORT ADMINISTRATION ACT OF 1979 (50 U.S.C. App. 2401) and/or ITAR.
The transfer, export or disclosure of technical data covered by these laws to any non U.S. citizen without a license or exemption from the U.S. Department of State is prohibited and violations may result in criminal, civil or administrative penalties.
--
You received this message because you are subscribed to the Google Groups "frePPLe users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to frepple-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/frepple-users/d7923dd9-02e9-4458-977a-e01e19313b6an%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/frepple-users/365c66a1529ca8f0a23191210a358bac%40mail.gmail.com.