Audited commands and a simpler Jobs tab
Manual command and job runs now record who launched them. The interactive browser terminal has been removed.
The service’s Jobs tab continues to support one-off commands and scheduled jobs. Manual runs now create an activity event identifying the person who launched the run and the service it belongs to.
Review who ran an operation
Use the activity feed to identify a manual run, then inspect the execution record for its command and output. Command text stays in the run record rather than being copied into the organization-wide activity feed.
Interactive terminal removed
The interactive browser terminal is no longer available. For tasks such as a maintenance command, use a one-off command in Jobs. Recurring tasks can continue to use scheduled jobs, and deployment migrations can use the service’s pre-deploy command.
This changes the terminal feature announced in the August Jobs release; it does not remove one-off commands or scheduled jobs.