Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove total_interactions metric for CAROUSEL_ALBUM #19

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

diwakarkasi
Copy link
Contributor

@diwakarkasi diwakarkasi commented Mar 7, 2024

IG pipelines started failing on Mar 7, 2024 with the below error:
400 Client Error: Bad Request - (#100) Incompatible metric (total_interactions) with the media for path: /{media_id}/insights
Screen Shot 2024-03-07 at 5 35 27 PM

The error seemed to be specific for CAROUSEL_ALBUM though the IG API docs still mention about using total_interactions metric.

Screen Shot 2024-03-07 at 5 36 06 PM

The pipeline ran successfully from local with this change.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

help me understand what this is doing. if media_product_type is ad or feed and media_type != video then we're adding total_interactions and we're also removing it from media type carousel album? did they move the metric? why does this work?

Copy link
Contributor Author

@diwakarkasi diwakarkasi Mar 8, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To your first statement, yes thats what is being done. To the second, I have no idea... the pipelines started failing with this error all of a sudden and the API docs didn't suggest anything about removing this metric. Here is one useful thread I found but thats still unresolved.

https://developers.facebook.com/community/threads/1094518705074298/

More importantly, the pipelines this morning (Mar 8th 2024) ran just fine with no issues.

So looks like Meta was being Meta and just wasted sometime of ours.

So we could probably leave this PR out here for now and I will close it after a few days if there are no interruptions.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

haha okay leave it open and i guess this is a small enough detail that we don't need to fully understand it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants