Efficient recurring tasks, clearer failures, and worker renames
This week made recurring tasks more efficient, made problems easier to see from your side, and made new workers steadier at getting started.
More efficient recurring tasks
Each run of a scheduled task now starts its own conversation instead of carrying every earlier run's history. A task that has been running for months gives each run focused attention, and the 200th run is as efficient as the first, which means savings for you on long-running tasks.
A clear notice when a connection stops working
When a connected app's sign-in or key is no longer valid, the person talking to the worker is told plainly what failed and who can fix it. The connection's owner is told what to do next.
No more silence after a failed turn
When a worker can't be reached or a turn fails, the person who wrote to it now hears that something went wrong. Before, they could get silence or a misleading “complete”.
Renames reach Slack
Renaming a worker now updates the name of its installed Slack app within a couple of minutes, with no re-install. The worker introduces itself by its new name on its next turn.
Fixes
- New workers more reliably go to work. Setup is steadier, so a newly created worker is more likely to come up and start working the first time.