Join our Community in its new Home - The Datorama Trailblazer Community Group!
It's been an amazing 3 years coming together in this forum to collaborate, innovate, support, and inspire each other about our shared usage of Datorama. While this is not quite a goodbye, we are excited to announce that we are getting a fresh start in our new home within the Salesforce Trailblazer Community. We have a ton of fun new content planned and you may even see the revival of some of our most popular posts from the past few years.
We’ll be keeping this group around for a bit for you to peruse, but as of November 15, we will no longer be allowing new posts or comments. Be sure to join our new group at https://www.salesforce.com/success-datorama to keep the conversation going.
We can’t wait to see you there!
It's been an amazing 3 years coming together in this forum to collaborate, innovate, support, and inspire each other about our shared usage of Datorama. While this is not quite a goodbye, we are excited to announce that we are getting a fresh start in our new home within the Salesforce Trailblazer Community. We have a ton of fun new content planned and you may even see the revival of some of our most popular posts from the past few years.
We’ll be keeping this group around for a bit for you to peruse, but as of November 15, we will no longer be allowing new posts or comments. Be sure to join our new group at https://www.salesforce.com/success-datorama to keep the conversation going.
We can’t wait to see you there!
Facebook Datastream "Profile or Sub-Profile not exist" Error


in Help Center
Has anyone else encountered the "Profile or Sub-Profile not exist" error when processing a Facebook Ads datastream? This error just appeared 5/23 on a datastream that had been working fine all year.
Datorama pushed out a system message on 5/28 saying it was a known issue, but do not yet have an answer. It's unclear if the issue is in Datorama, or on the Facebook side.
Has anyone encountered this and found a reason/solution?
Datorama pushed out a system message on 5/28 saying it was a known issue, but do not yet have an answer. It's unclear if the issue is in Datorama, or on the Facebook side.
Has anyone encountered this and found a reason/solution?
Tagged:
Best Answer
-
RTW2 Boston, MAACCOUNT_ADMIN
Facebook published a fix this morning that at first glance appears to have solved the problem.
Answers
The best way to proceed in this case would be to log a ticket to [email protected] so our Support team can take a look at the exact streams in your Workspace and thus advise you further.
In the ticket, please provide your Workspace ID and the IDs of the failed streams in order to facilitate the troubleshooting process.
Let me know if any further questions arise.
Best,
Tsvete
Forced to pull data manually from FB and import via TotalConnect stream in the interrim (not ideal).
System Notification
To our valued Datorama Users,
Please be aware that some Facebook API Data Streams are failing due to an error 'PROFILE_OR_SUB_PROFILE_NOT_EXIST' received by the provider, resulting in missing data. This is a valid response from the Facebook API upon lack of permissions for the credentials used - but seems to be occurring more recently due to an issue with the provider.
We are actively investigating the issue alongside Facebook and an issue has been submitted on this to the provider.
Please also validate that the credentials being used do in fact have Admin access to the needed accounts which allows API calls.
Once the issue is resolved, the Data Streams will automatically re-process all the failed jobs
May 28, 2019
And to this active Facebook Bug report:
https://developers.facebook.com/support/bugs/354961795132632/
Seems to impact only facebook-ads datastreams that are connected to fb business accounts that are owned by a 3rd party clients (but managed by an agency, for example). Surely there are other Datorama users impacted by this bug.