Two jobs with same filter are pulling different quantity of records

  • 30Views
  • Last Post 26 December 2018
0
votes
Skyvia Integration posted this 16 November 2018

We recently setup a new package (57896) that pulls different fields of data from Salesforce, but it has the exact same filter as another package (45484) that we have been running for months. Both jobs are set to run hourly thorughout the day, however I am seeing that in some hours the new package (57896) is pulling more records, but the hour before and hour after they have the same number of records (see attached). Any way I can determine the cause? if it was the couple fo minutes difference in the run times, I should see them equal out at some point, but they are not.

 

Attached Files

Order By: Standard | Newest | Votes
0
votes
Mariia Zaharova posted this 26 December 2018

Thank you for the reply. We continue to investigate this case and we will post here news as soon as any is available.

0
votes
Skyvia Integration posted this 21 December 2018

We are no longer using job 45484, but my concern is whether any of the jobs are pulling all of the records they should be. Just because 57896 was pulling more records doesn't mean it wasn't skipping records like the other job. 

0
votes
Mariia Zaharova posted this 21 December 2018

Hello! Unfortunately, we were not able to detect the reason of such a behaviour. Whether you are still encountering this issue with the mentioned packages?

 

Best regards,

Mariia

0
votes
Skyvia Integration posted this 20 December 2018

Just wanted to follow up and see if anyone is actually looking into this or there was anything found. 

0
votes
Mariia Zaharova posted this 20 November 2018

Thank you for your answer. Yes, we can see the difference, however, we cannot tell you any possible reason for this issue at the moment. We will investigate this case more clearly and contact you if any news is available.

 

Best regards,

Mariia

0
votes
Skyvia Integration posted this 19 November 2018

Mariia - unfortunately, the sales team does not work over the weekend, so that is not a valid timeframe to look at for records. Please use today and/or tomorrow. 

0
votes
Mariia Zaharova posted this 19 November 2018

We have checked 20 last runs of these packages and they produce the same results. Whether the issue is still actual?

 

Close