Skyvia jobs failing again

  • 80Views
  • Last Post 17 April 2018
0
votes
Skyvia Integration posted this 22 March 2018

For the last two hourly runs for a job to export Quotes and Quote lines has failed with the following error:

SBQQ__QuoteLine__c (The remote server returned an error: (404) Not Found.)

I confirmed the User that Skyvia uses has not been changed and the login history is showing that it is successfully connecting. No fields have been deleted from these Objects and I cannot think of anything on our side that would be causing this.

I just ran the job manually, and it worked, but I don't understand why the last two scheduled runs failed.Please advise. 

Order By: Standard | Newest | Votes
0
votes
Mariia Zaharova posted this 23 March 2018

This error may occur because of high server load. For example, if several export packages start at the same time, while we create a separate session for each of them. In case if several packages access Salesforce simultaneously, the Salesforce server may fail to process some of the requests. This situation is unlikely, but possible. 

We recommend you check this and try scheduling your packages so that they started at different time (for example, each next package one minute later than the previous one). So that the second package started a minute later than the first one, the third one a minute later than the second, and so on. 

JIC: As we can see, the package #37099 "Salesforce SPL Export - Production" works as expected for now.

1
votes
Skyvia Integration posted this 23 March 2018

Looking at the jobs throughout the day, none of them ever start at 0 minutes past the hour or even the time they are "scheduled" for, and start time will vary 2-5 minutes from hour to hour due to load. I have 2 jobs that run hourly - from 9:00-6:05 and 9:05-6:10 respectively - and one that runs hourly, 24/7 that does not actually have a start time, unless you count the original schedule from when the job was created back in November, which was set at 58 minutes after the hour. Other than one import job that runs after 6 PM, none of the jobs are more than 200 records at a time. I realize it is not just my jobs that are taking up the "server load", but it sounds like you need more processing capability and not arbitrary schedule settings that are treated as suggestions.

  • Supported by
  • API User Reporting
-1
votes
Mariia Zaharova posted this 26 March 2018

The user community was told this problem should not happen any more because of changes you made.

 I realize it is not just my jobs that are taking up the "server load", but it sounds like you need more processing capability and not arbitrary schedule settings that are treated as suggestions.

The issue posted here is not related to the issue that had Skyvia two weeks ago (with the stuck/queued packages). The "SBQQ__QuoteLine__c (The remote server returned an error: (404) Not Found.)" error occurs on the Salesforce side and is related to high load on Salesforce server. As we have said above when many requests are sent to Salesforce simultaneously, the Salesforce server may fail to process some of them and Skyvia cannot control this due to the fact that operations fails on the source side (Salesforce).

 

1
votes
Mariia Zaharova posted this 27 March 2018

Skyvia needs to be aware of this possiblity and have appropriate retry logic in replication packages. 

The issue discussed here is related to Export packages, not Replication ones. Darryll, we have answered you regarding all the issues you have reported regarding replication in the corresponding topics.

As for the retry logic in scheduled packages, we plan to implement this functionality in future Skyvia versions. We will post the results here as soon as any are available.

 

Due to the fact that the "The remote server returned an error: (404) Not Found." error occurs at Salesforce side and reproduces inconsistently, we cannot give you the exact reason why it occurs.

We assume that this error can occur when, in the case of sending numerous authentication requests to the Salesforce service, some of these requests are not processed by Salesforce and this leads to this error. Also, this error can occur if a custom domain is used - for some reason, the redirection of authentication requests fails.

If this error occurs with any of your packages consistently, then we will try to test it and give you more details on it.

 

  • Supported by
  • API User Reporting
0
votes
Skyvia Integration posted this 11 April 2018

It happened again in back-to-back hours this morning. Is there anything else we can look at from this side to determine the cause? Would there be any point to opening a ticket with Salesforce?

0
votes
Mariia Zaharova posted this 17 April 2018

Sorry for the late response.

Would there be any point to opening a ticket with Salesforce?

We recommend you to reduce the frequency of performing packages and, if this doesn't help, to contact Salesforce support with this issue.

Close