Slack retries are protecting task completion while duplicating completed updates.
The harness must recover from late tool responses without making colleagues clean up repeated messages.
Who you’d be doing this for
“I had three people ask whether the same update meant three separate changes.”
Ato Adekunle · Research Operations Manager
Coordinates internal research requests and depends on Slack updates to keep reviewers aligned.
What is at stake
Duplicate Slack posts now affect 3.8% of completed posting tasks. You must weigh fast recovery from real failures against the credibility lost when completed work repeats.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- task recovery vs duplicate outward actions
- simple configuration vs action-aware state
- release speed vs replayable evidence
Why Perplexity
Perplexity Computer turns research into actions across Slack, so a repeated post damages confidence in delegated work.
Written with these in mind
Not your kind of problem? 31 more at Perplexity, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.