You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I ran the proc: EXECUTE [procfwk].[ResetExecution] for a failed batch middway of execution.
How then do I get it restarted because the proc says it will be ready for restart but if I execute the main pipeline it fails because it checks to see if a pipeline is running in sql which that proc makes it look like it is running but in reality nothing whatsoever is even happening ?
Regards,
Michael
The text was updated successfully, but these errors were encountered:
If you update the procfwk.BatchExecution table and set the BatchStatus for the failed batch (that is currently at BatchStatus
'Running') to 'Stopped' you can then trigger the Parent pipeline with that batch name as a parameter to restart the batch.
That said, this should be done in the ResetExecution procedure or through some other mechanism - Ideally checking if the pipeline is ACTUALLY running for that batch and updating it on reset.
The fix for this should be in 2.1 beta. Adding 3 retries for all activities that access the metadata db resolves a number of issues that leave the metadata in an inconsistent state. Errors accessing the metadata db have been our number 1 issue.
Hi,
I ran the proc: EXECUTE [procfwk].[ResetExecution] for a failed batch middway of execution.
How then do I get it restarted because the proc says it will be ready for restart but if I execute the main pipeline it fails because it checks to see if a pipeline is running in sql which that proc makes it look like it is running but in reality nothing whatsoever is even happening ?
Regards,
Michael
The text was updated successfully, but these errors were encountered: