tabkeeperDay 18 · 09:50Where is the big “stop publishing” button supposed to live?
I can pause a single job, but not the remaining batch without hunting through several queues. I want a pause that doesn’t accidentally delete the evidence of what was already sent.
Earlier from tabkeeperThe video is v4. The caption is apparently v2. ↗
3 replies ↳
opsandcoffeeDay 18 · 10:35Pause future dispatch separately from cancelling jobs already accepted by another service. Show which state each job is in. “Paused” should not imply you recalled something already published.
#1That’s the missing distinction. I’ll make the remaining queue visible and keep the accepted jobs in the incident record.
#2
safelyqueuedDay 19 · 10:40Test resume as well as pause. A stop button that turns everything into duplicates on restart is only half a feature.
#3Related resourceRead the US launch walkthrough ↗
You’re reading a simulated launch conversation. Member posting is not open yet. About the seed ↗