Participant

Content Scheduler: "An error occurred" on Schedule, post silently missing on some selected channels

Forum|Forum|11 days ago
August 30, 2026
2 replies
7 views

Paid Adobe Express subscriber (Premium), web version, Chrome on Windows. I schedule around 20 posts a week to Facebook, Instagram, LinkedIn, TikTok, X and YouTube through the Content Scheduler.

ISSUE 1 - scheduling fails, and fails silently on some channels

When I select several channels and click Schedule, I regularly get "An error occurred, please try again later". After refreshing, the post exists on some of the selected channels but not on all of them, with no per-channel error telling me which ones were dropped. A scheduling session that used to take 20 minutes now takes 40+ minutes because I have to refresh constantly and re-check every channel by hand.

This is not new and it is not a one-off. It has been happening for a long time and has been getting worse. I am reporting it now because it has become a weekly cost.

ISSUE 2 - every LinkedIn post failed 22-31 July 2026

All posts scheduled to LinkedIn on 22, 23, 24, 29, 30 and 31 July 2026 are marked Failed, on both of my LinkedIn channels. The error on each is: "Post failed. Unfortunately, your LinkedIn post failed. Please retry publishing your post, or refresh your LinkedIn connection before retrying."

Example failed post ID: 839f837e-b097-4e50-82e9-0ce79d0cae72

LinkedIn posts published fine from 1-21 July and again through August. At the same time, the Connections panel showed both LinkedIn accounts as Connected with a green check - so the error told me to refresh a connection your own UI reported as healthy.

WHAT I HAVE ALREADY RULED OUT

- I disconnected and reconnected all social accounts. The error still happens.

- No calendar filter is hiding posts.

- My Pinterest channel previously showed as "Not connected" and after the reconnect round it disappeared from the Connections panel entirely. I did not delete it.

FRONT-END ERRORS ON YOUR SIDE

On a normal load of the Scheduler, the browser console reports dependency-injection timeouts from your own scripts:

"Locator: factory for HomeRecentBarStore not provided through Locator.set() within 20000 ms" and the same for FeaturedBrandStore, from hz-startup-ui-index.js. That is a 20-second timeout inside your application, and it matches how slow the page is every time I reload after an error.

WHAT I AM ASKING

1. Is this a known issue, and is there a fix or an ETA?

2. Can you check server-side logs for my account for the July LinkedIn failures and for the "An error occurred" responses when saving a scheduled post? Happy to send my Adobe ID by private message.

3. Please make the Scheduler report per-channel results instead of one generic error. Silent partial success is the worst part of this bug.

SMALL UX BUG WHILE I AM HERE

The calendar filter state persists across reloads and browser restarts, and the only indication is a tiny badge next to the funnel icon. If "Failed" is left checked, the calendar looks completely empty and it reads as data loss. Please show the active filter as text.

Rose DV

Community Manager

Hi @daring_Cosmos5e93,

This is one of the most thorough reports I've had come through, so thank you for taking the time.

You've clearly already done the troubleshooting (reconnecting accounts, checking filters), so I'm not going to send you back through any of that. I'm taking this to our team as a Scheduler reliability issue, and I want to make sure the distinct pieces don't get flattened into one, because they may be separate:

→ The silent partial-failure on Schedule (posts landing on some channels but not others, with only a generic error): this is the core one
→ The LinkedIn failures across 22–31 July specifically, while your connections showed healthy
→ The console dependency-injection timeouts you're seeing on load

On your asks: the request for per-channel error reporting instead of one generic "An error occurred," and showing the active calendar filter as text, are both fair and I'll pass them along as feedback to the product team.

A couple of things will help the team look into your account directly - but let's not post them here: I'll follow up by DM for your Adobe ID so it can be attached to the report securely, rather than on the public thread. If you can also confirm the rough time (with timezone) of one recent "An error occurred" so they can line it up with server logs, that'd help them trace it.

I'll update you here as I hear back.

Rose

Rose DV

Community Manager

Hey @daring_Cosmos5e93,
Thank you again - your detailed report made it straightforward to get each piece logged with our team. Where things stand:

The LinkedIn failures across 22–31 July: it was a platform-wide issue affecting LinkedIn publishing during that window — not anything specific to your account or your connections (which is why your UI correctly showed them as healthy). It's since been resolved, and the team is adding safeguards so that class of failure is caught earlier in future.
The core issue - scheduling to multiple channels and having some silently fail with only a generic error - is logged and with the team, including your point that it needs to tell you which channels failed rather than a single "an error occurred." That per-channel reporting is part of what's being looked at.
Your other points are captured too: the calendar filter making things look empty, the slow reloads/console errors, and the Pinterest channel dropping off the Connections panel are all recorded.

I don't have fix dates to share yet, and I'll be straight with you rather than promise timing I can't back up - but these are in the right hands now.

On the account-specific side, if you're still up for sending the rough time (with timezone) of one recent "an error occurred," the team can line it up with logs on their end.

I'll keep you posted here as I hear back.

Rose

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.