Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

The pipeline ran well the first time but didn the second time. What could have gone wrong?

April 26, 2017gone pipeline ran time wrong

0

Posted

The pipeline ran well the first time but didn the second time. What could have gone wrong?

1 Answer

0

Posted

There could be many reasons for this. The most probable reason could be that you failed to empty the output and job tables after running the pipeline the first time. You might get a message like this: Tests Completed. Starting Pipeline Fetched 0 jobs Waking up and run again! The two tables have to be reset everytime the pipeline is run.