Update - As of 4/4/2018 Instagram has abruptly retired their API that allowed for users to perform a public search for other users content. For example, you can no longer search for @storyports Instagram content unless the @storyports user was the one who authenticated the channel. This change was supposed to come into effect December 11, 2018 but was immediately released by Instagram for unknown reasons. The following will outline the impact to customers and steps to get content flowing back into your content blocks.

Impact to Customers:
- Any email with Content Ctrl Instagram block will trigger ET Raise Error and fail the email send.
- Any public search in StoryPorts Studio will fail and return an error message
- Any email with an Instagram Stream that uses public search (which is all of them) will:
> In App - will display error message in email body.
> On Publish - No content will display. Area will remain empty.

To get content to populate correctly again you will need to follow these steps.

Content Ctrl Users:
- Navigate to Connectors / Instagram
- Re-Authenticate all Channels to User Credentials for media you want displayed
- Access Content Blocks and Clear Search Fields for Hashtag Search and User Search. This will display the authenticated user’s media by default.
vRepublish
- Note: Any email with Content Ctrl Instagram block will trigger ET Raise Error and fail the email send.

StoryPorts Studio Users:
- Navigate to StoryPorts Studio
- On Search, Select Instagram
- Under the Instagram Icon, Select the dropdown arrow
- A dialogue will appearch. Select the Gear Icon
- Select Re-Authenticate
- Provide Instagram Permissions
- If you have multiple channels, do the same process for each channel.
Apr 4, 18:09 EDT
Identified - Instagram content using "public search" no longer returning content. We will keep you updated with the details as we uncover them.
Apr 4, 16:19 EDT
Monitoring - As of 12/5/2017, We have identified and are monitoring an intermittent issue that affect Streams in email. You may experience issues with Streams and/ or Scheduled Content displaying improperly. The frequency of impact is every 100- 200 incidents of a Stream refreshing in an email. To determine if a stream has been impacted by this error, you will see the following error message in the content area where the stream is located:
{"result":"ERROR","status_code":"FUN17","error_msg":"Template file missing: ... "}
Please monitor any scheduled or automated email sends that include Streams of content. Thank you for your patience.

If you have an urgent issue: Contact us via InApp Chat, or Adrienne@Storyports.com.
Jan 5, 14:13 EST
Content Engine   Operational
Automation Engine   Operational
Rendering Engine   Operational
Web Services   Operational
Outbound Connectors   Operational
Inbound Connectors   Operational
Tracking Engine   Operational
CDN   Operational
API   Operational
Login Page   Operational
Website   Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
StoryPorts Automation Engine
Fetching
StoryPorts Databases
Fetching
Past Incidents
Apr 24, 2018

No incidents reported today.

Apr 23, 2018

No incidents reported.

Apr 22, 2018

No incidents reported.

Apr 21, 2018

No incidents reported.

Apr 20, 2018

No incidents reported.

Apr 19, 2018

No incidents reported.

Apr 18, 2018

No incidents reported.

Apr 17, 2018

No incidents reported.

Apr 16, 2018

No incidents reported.

Apr 15, 2018

No incidents reported.

Apr 14, 2018

No incidents reported.

Apr 13, 2018

No incidents reported.

Apr 12, 2018

No incidents reported.

Apr 11, 2018

No incidents reported.

Apr 10, 2018

No incidents reported.