Slash SocialLumen Trail
Needs attention
Threads account needs attention
Thursday's launch recap is protected until the account is reconnected.
Account health · Queue protectedAccount health
Catch account issues before posts fail.
Watch account connection state, expired tokens, reconnect needs, and platform-specific blockers from the same Slack workflow as publishing.
All plans
Publishing
App Home flags the blocked account.
This is a readiness workflow, not a generic unhappy-path card.
Slash Social#generalShared social workflow
Today
🧵
Launch recap thread
Threads · Post
- Description
- Launch recap post
- Status
- Ready to publish
- Window
- Thu 2:00 PM
- Account
- Threads connected
MC
This customer note fits Friday's trail education post.
Message #general
Why it matters
Catch account issues before the queue fails at publish time.
- Connection status for social accounts
- Reconnect prompts for expired or disconnected accounts
- Publishing blockers surfaced in Slack
- Platform-specific status tied to each target
In Slack
See account health where the team will use it.
The preview below shows how account health appears in Slack — the context, entry points, and next actions your team uses every day.
How does account health reduce surprise failures?
It shows the account, affected queue items, owner, and reconnect path before the scheduled publish window.
A reconnect alert before the queue breaks.
The artifact shows connection state, affected accounts, owner, and recovery action before a scheduled post reaches failure.
- Where it lives
- Account health alert
- Visible workflow
- Disconnected or expired accounts are visible before publish time
- Decision
- Reconnect, assign owner, or pause target
AccountExpired
@acme_social expired
Instagram target needs reconnect before Friday's Reel.
OwnerAssigned
Route to channel admin
The person with account access gets the recovery action.
QueueAt risk
2 posts affected
The team sees what will fail if the account is not restored.
Related Slack entry points
- Reconnect account
- Account health queue
- Publishing blocker alert
Treat account health as part of publishing.
A scheduled placement cannot ship if the target account needs attention. Slash Social makes that state visible before the team assumes the queue is healthy.
Put reconnect work in front of the right owner.
Teams can see which account needs action and route the reconnect to someone with the right access.
Keep platform status attached to the item.
Each platform target can carry its own status so one blocked account does not hide the rest of the work.
Outcomes
What your team gets from account health in Slack.
Token expiry and connection errors surface in Slack before the scheduled slot, with the account and owner named.
Account-health alerts assign reconnect or re-auth work to a billing owner or social lead, not the whole channel.
Your queue shows which targets are ready to publish and which still need account attention before go-live.
FAQ
Account health questions
Can one platform fail while others continue?
Yes. Platform targets can carry separate state, which helps teams understand what shipped and what needs attention.
Can account issues show up in Slack?
Yes. Account and publishing blockers can surface where the team can act on them.
Ready when your team is
Bring account health into Slack.
Start with the workflow that hurts most, then connect the rest of your social operation around it.