Logs need to contain more information about the errors
The way to solve this is to update the system to make it think that the records have not yet been processed. This is not very straightforward, and if done incorrectly, could result in duplicate entries in the utilization metric. We worked with Swetha to understand how to re-run these metrics if we needed to. She gave us explicit direction on how to reset the system. This is my understanding of what needs to be done:
Go to the ServiceMax processes tab
Find the process related to Utilization (in production, PN-0000009885)
Scroll to the related list ServiceMax Config Data (Dispatch Process)
Open the configuration for “Schedule”
Change the “Previous Execution Started On” date and “Previous Execution Completed On” to before June 7
Delete all of the Utilization records for that time period to avoid duplicate entries. There is no easy way to do this except writing some sort of SQL to do a mass-delete. Swetha was unsure if the engine would make the duplicates or not, so we have done this step as a precaution.
Re-run Utilization. It should then pick up the records from whatever date we set.
What is the underlying problem do you intend to solve with this idea?
More concrete details on errors and error logs archived longer to help investigate issues and conduct thorough analysis