I noticed the Weekly CCC Module Metrics has been showing as succeeding in the GCP scheduler, but it hasn't produced the report to Box in two weeks. I was able to fix the root of the problem, but I would need these types of instances to consistently show as failure in the scheduler so I know when they aren't producing the reports. For clarity, the code would not finish running through the libraries chunk (likely because of missing libraries in the Docker) so it would never move passed that point in the logs.
Is there a way to force a failure if the "All done. Check (scheduler) for (report).pdf ...." message isn't eventually generated or other sort of force fail? Please let me know if anything is needed on my end!
I noticed the Weekly CCC Module Metrics has been showing as succeeding in the GCP scheduler, but it hasn't produced the report to Box in two weeks. I was able to fix the root of the problem, but I would need these types of instances to consistently show as failure in the scheduler so I know when they aren't producing the reports. For clarity, the code would not finish running through the libraries chunk (likely because of missing libraries in the Docker) so it would never move passed that point in the logs.
Is there a way to force a failure if the "All done. Check (scheduler) for (report).pdf ...." message isn't eventually generated or other sort of force fail? Please let me know if anything is needed on my end!