A graph was scheduled to run twice a day.
Some time later, Scheduling was showing Previous and Next event times correctly implying that scheduler invoked the graph but nothing actually ran. Execution History showed nothing. How would one detect an error to start a graph?
An attempt to run graph manually without the schedule revealed an error in the graph. The message was "Metadata cannot be instantiated" because of a missing metadata definition file.
Some time later, Scheduling was showing Previous and Next event times correctly implying that scheduler invoked the graph but nothing actually ran. Execution History showed nothing. How would one detect an error to start a graph?
An attempt to run graph manually without the schedule revealed an error in the graph. The message was "Metadata cannot be instantiated" because of a missing metadata definition file.
-
Hi,
The reason for this is because your graph is searching for a externalize metadata file that its not in the correct path. You will need to find the file and add it to the correct path. The metadata file which is causing the problem should be visible in the Outline > Metadata section of the Designer. -
The question is not why the graph failed to start. The question is whether there is a way do detect such a failure?
A situation could arise where initially the graph is defined properly and is scheduled to run periodically. Then, sometimes later the graph or elements it depends on are corrupted. How can subsequent failures to start the graph be detected? -
Hi Jacob,
Just wanted to summarized what was discussed, you were running an older of CloverETL Server that was not notifying you of the error, I suggested to upgrade to a higher version 4.1 which features the "Save run record". Alternatively, you can track the error in the Clover ETL server logs (all.log files).
Please sign in to leave a comment.
Comments 3