new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

Temporal · Concepts · all subjects

retention & persistence

3 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

workflow delete - asynchronous removal

The workflow delete command deletes a Workflow Execution and its Event History. The removal executes asynchronously. If the Execution is Running, the Service terminates it before deletion.

workflow delete in global namespace

Deleting Workflow Executions in a global Namespace removes them from all replicas. Requests sent to a passive cluster are forwarded to the active cluster by default; to target the passive cluster directly, specify --grpc-meta xdc-redirection=false.

workflow delete flags

workflow delete command flags: --headers (string[], optional): Temporal workflow headers in KEY=VALUE format; --query/-q (string, optional): SQL-like Query List Filter; --reason (string, optional): Reason for batch operation, only with --query, defaults to user name; --rps (float, optional): Limit batch requests per second, only if query present; --run-id/-r (string, optional): Run ID, only with --workflow-id, cannot use with --query; --workflow-id/-w (string, optional): Workflow ID, must set either --workflow-id or --query; --yes/-y (bool, optional): Don't prompt to confirm, only with --query.

Give your agent this brain