Error Package One Table

  • 56Views
  • Last Post 13 April 2022
0
votes
Gabriel Longarai posted this 07 April 2022

Hello, when there is failure in one table and success in others within a package, the process as a whole is successful. And the lastSync parameter has the last run date. This situation happens in the package below (Run Id 87367627).

Is it possible to change the way the package is executed? It would be better not to update lastSync when one or more tables in a package fails.

 

https://app.skyvia.com/#/76069/packages/156228/debug

Run Id 87367627

 

 

Attached Files

Order By: Standard | Newest | Votes
0
votes
Nataliia Nikulina posted this 11 April 2022

Hello Gabriel,

Thank you for contacting the Skyvia Support team.

The package is validated before execution and if there are any errors at this stage, they can bring down the package.

But when the processes have already started in parallel, they are independent. Only if all tasks are failed, then the package declared as failed.

Regarding the date of the run, all tasks are executed in parallel so we cannot undo those actions that were committed that's why the LastSync parameter is updated.Otherwise, the rest of the tasks will then start pulling data again and this is undesirable behavior.

As for the error in your package, it looks like a temporary internal issue but please inform us if it happens again.

 

Best regards,

Nataliia,

Customer Support Engineer 

 

 

0
votes
Gabriel Longarai posted this 11 April 2022

But in this case it becomes a big problem. Because, when only one table fails and the packet succeeds, we do not receive an alert that an error has occurred, causing records to be lost, and our analyzes to have wrong numbers.

And the other problem is that to adjust this, we will have to drop all tables and reprocess again, since lastSync is updated.

And the number of lines in this package, which is about 2 million, will have to be loaded, that is, if this package fails twice a month, we will exhaust our monthly limit.

The right thing would be: either not to update the lastSync, or to have a lastSync for each table inside a package, or in the initial validation of the package, to verify that there is the same column structure in the source and in the destination.

0
votes
Nataliia Nikulina posted this 13 April 2022

Hello Gabriel,

Thank you for the update.

We have passed your request to our technical team. We will let you know once we have any updates.

Should you have any further questions, let us know.

Best regards,

Nataliia,

Customer Support Engineer

Close