Receiving error related to marketing_campaigns.read

[adifferentjoel]

I saw there was a revert of some code the other day, however I'm still seeing this error inside Stitch: INFO Exit status is: Discovery failed with code 1 and error message: "Insufficient authorization, missing for marketing_campaigns.read".

Any ideas what is happening?

[stevebuckingham]

We have also seen the same error:

2019-12-16 13:56:26,495Z   main - INFO Tap exited abnormally with status 1
2019-12-16 13:56:26,497Z   main - INFO No tunnel subprocess to tear down
2019-12-16 13:56:26,498Z   main - INFO Exit status is: Discovery failed with code 1 and error message: "Insufficient authorization, missing for templates.versions.read,marketing_campaigns.read,templates.read,asm.groups.read,suppression.read".```

[rsest]

I have the same error:
main - INFO Exit status is: Discovery failed with code 1 and error message: "Insufficient authorization, missing for marketing_campaigns.read".

[DylanBaker]

Hey. I'm getting the same error here. Is there any timeline on this?

[MattBurlew]

Same error for me as well.

[shedd]

I am also running into this. I tested this first with an API key configured as per the documentation here: https://www.stitchdata.com/docs/integrations/saas/sendgrid-core#create-a-sendgrid-general-api-key

Then I tested this with an API key with full access. Both configurations returned the same error.

[shedd]

From doing a little bit of reading about this, it seems that the requirement for this marketing_campaigns.read scope has been a bit of an issue.

It was removed and then re-added in this PR: #3

This comment on the PR - #3 (comment) - also indicates that Support can manually add this scope. I've opened a Support Request with SendGrid and will report back if this approach is successful.

[shedd]

SendGrid support replied:

The [marketing_campaigns.read] scope you are referencing is a legacy Marketing Campaigns scope. The Legacy Marketing Campaigns feature is no longer available, unfortunately. As such, I wouldn't be able to add that scope on your behalf.

As such, not sure why this was re-added after being removed in #3?

[garrypolley]

This issue prevents new integrations from working that do not use the legacy APIs. In contacting SendGrid support this is because clients using the new marketing features do not have the old scope available. Further the data will not be accessible under the old API and scope.

Is there anything folks can do to help un-revert the scope request?

[RandallKent]

@KAllan357 - Curious if you had thoughts on this. Perhaps it would make sense to release a v2 of this tap with support for the current SendGrid API?