We had awidespread failures of many replication packages starting at about 7am ET yesterday. It does appear that they are starting to work again as of 4am ET today. Isd this a known issue -- possibly related to th new run engine? Is this resolved?
Multiple Packages Failed
- Last Post 17 April 2020
The first three packages I looked at all failed for extended periods yesterday. Other packages looked ok. The failed package names are:
- Replication - Azure QDB01 - Temporal Store - Salesforce Objects - 01
- Replication - Azure QDB01 - Temporal Store - Salesforce Objects - 02
- Replication - Azure QDB01 - Temporal Store - Salesforce Objects - 03
Your response is both timely and factually correct. In many respects the most important issue is how quickly we can get things working again. Then again, it might be comforting to know that we won't have a 20 hour gap where things stop working again. Any guess what happened? Was this an issue with our data source or target systems, or with your engine? How likely is it that we will see future disruptions? Why was the error message so uninformative?
Thanks again for your timely response. Thanks for getting things working agiain.
It was an internal issue on our side related to the packages where SystemModstamp is used. Details of the error were available only in our internal logs. At the moment, the issue is fixed and it will not appear again.
At the moment, we are working on improving error package logging in the new engine (the "Use new runtime" option), so that you are able to see more details when clicking on the failed run.
Sorry for the inconvenience with this and thank you for using Skyvia.