Salesforce Spoke scheduled jobs failing, OAuth token fine

HeyMarkWarmack
Tera Expert
Dear Community - 
Is there someone that is successfully using the Salesforce Spoke and getting the SaaS Subscriptions and Consumption data downloaded.
Mine broke a while back without me seeing that it failed, went thru at least one SN upgrade and possible other Salesforce updates.
We ARE getting the OAuth 100 day token, it connects, the Salesforce Scheduled Jobs just fail.
>> SAM - Refresh Salesforce CRM Subscription Subscriptions
>> SAM - Refresh Salesforce CRM Subscription Consumption
ERROR: Failed to download consumption.
 
* I have tried different Run As' users, ones with ITIL and Salesforce Admin and I get the same error.  I have tried blank Run As and System Administrator as Run As user.
* I have updated the Salesforce Spoke - Salesforce Spoke App Id: sn_sforce_v2_spoke v2.3.4
* Verified  'scope' on the Salesforce side is defined.
* I have checked and rechecked the Workflow Designer Salesforce Connection, checked all the individual OAuth and Registry profile information.
* We built out a DEV Sandbox and made a dozen tweaks, been thru the Salesforce KB and extinguished all the knowledge out there and currently going back and forth.
* I have an OAuth for Microsoft and did not have this much issue getting it fixed when it broke.
I don't know the intricacies of Salesforce to know what I am missing.
Anyone wanna share some experience and knowledge?
6 REPLIES 6

kiran kumar m1
Tera Contributor

@HeyMarkWarmack did you got any solution on this

Kiran - 

I have not.  We setup a DEV sandbox and I believe adding SCOPE setting TO Salesforce did help a little bit, the errors changed but I have not resolved the issue in Production.

ANY suggestions are appreciated.

MikeW0609686430
Giga Guru

Have you checked the service account which logs into Salesforce to collect the information? Does it have the correct admin privileges?

i checked , the service account has the admin previlages , I raised a case with servicenow , they gave me a XML to upload , even after uploading the xml the jobs are not running as expected