Log unavailable

  • 102Views
  • Last Post 10 March 2021
  • Topic Is Solved
0
votes
Jessie Traynor posted this 17 August 2020

When running a package, we got some fualted records. However, when trying to download the log files, it comes empty, having only the message: 

 

"Error"

 

"Log unavailable."

 

 

 

Is there a way to get a detailed log?

 

 

 

Thx

Attached Files

Order By: Standard | Newest | Votes
0
votes
Mariia Zaharova posted this 17 August 2020

Hello Jessie,

 

We are investigating the issue. I will let you know the results as soon as possible.

 

JIC: did you try to run the package and check log in old Skyvia UI https://old.skyvia.com/ ?

 

Best regards,

Mariia

0
votes
Jessie Traynor posted this 17 August 2020

JIC: When I click on the package, throws an error:

 

1
votes
Mariia Zaharova posted this 18 August 2020

Hello Jessie,

 

The issue is related to the fact that your Import package uses Agent connection. 

Skyvia has not released full functionality for Agent connections yet.

At the moment, Agent connections can be used in Skyvia Query and Connect, and are available for Export (as a Source) and Replication packages (as a Target).

We are working on support for Agent connections in Import and Synchronization packages at the moment.

 

For Synchronization and Import packages only the connections created with Direct mode are available for now.

 

That's why you cannot download the log file and check your package in the old UI.

 

Best regards,

Mariia

  • Supported by
  • Jessie Traynor
0
votes
Andres Lobato posted this 09 March 2021

When running a package, we got some fualted records. However, when trying to download the log files, it comes empty, having only the message: 

 

"Error"

 

"Log unavailable."

 

i try old page, and show me error 404. 

 

my error happend when i try to replicate jira issues table to redshift.

0
votes
Mariia Zaharova posted this 10 March 2021

Hello Andres,

 

Unfortunately, we do not provide error reports for failed records for Redshift. This is because, when working with Redshift, records are processed in batches and it is impossible to get a complete report. 

After failed package run, please open Query Tool and run this query with your Redshift connection: 

select * from 'stl_load_errors'

 

You will get the table with the errors as a result.

 

Best regards,

Mariia

Close