Salesforce Spoke scheduled jobs failing, OAuth token fine
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-24-2025 01:41 PM
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
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Since the OAuth token is working and the service account has the correct permissions, it seems to me that the issue is on the Salesforce side. My recommendation is to verify the API permissions that have been set up in Salesforce.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
@MikeW0609686430 mikew - I agree. Just found out this all might be for nothing, looks like we are sunsetting it.
Thanks for all the engagement. I really wanted to find the root cause..... But agree, I was pointing to the Salesforce side too. 🙂
