Pacenote v0.3.6

The upgrade quits the running app first (the bot gets up to 20 seconds to finish its requests, and the rest resume on the next start) and reopens it. Config and run history are untouched.

A 👀 instead of a message

• When you mention Pace, it reacts to your message with 👀, and adds ⏳ if the answer takes longer than 90 seconds. Nothing is posted in the thread until the answer, so people talking there are not interrupted.
• The answer comes as a new reply at the bottom of the thread, so Slack notifies you when it is ready. (Before, it was edited into the "Working on it..." message, which Slack does not notify about.) The reactions come off once it is posted.
• A failure is a short reply too, and a restart keeps the 👀 on your message while Pace picks the request up again.

Add one scope to your Slack app

Pace needs the reactions:write scope for this. Until the app has it, Pace works as before, posting "Working on it..." and editing it into the answer, and the status bar shows "1 check issue" saying the scope is missing.

1. Open api.slack.com/apps and choose your Pacenote app.
2. OAuth & Permissions > Scopes > Bot Token Scopes > Add an OAuth Scope: reactions:write.
3. Choose "Reinstall to Workspace" in the banner at the top of the page, and allow it.

Pace picks the scope up with the next mention, without a restart, and the check issue goes away once a reaction works. If Slack shows a new bot token after reinstalling, save it in Settings > Messengers > Slack.

With a team hub, the hub's admin adds the scope to the hub's Slack app and updates the hub, which now lets each desktop react to the mentions routed to it.

Also in this release

• Settings > Messengers > Slack > Check connection passes without reactions:write and says what it changes.
• The run history links a run to your mention in Slack when there is no "Working on it..." message to link to.