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

visibility & search

9 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 count - show count regardless of state

The workflow count command shows a count of Workflow Executions, regardless of execution state (running, terminated, etc). Use --query to select a subset of Workflow Executions.

workflow count flags

workflow count command flags: --query/-q (string, optional): SQL-like Query List Filter.

workflow list - list executions

The workflow list command lists Workflow Executions. The optional --query limits the output to Workflows matching a Query. Archived Workflow Executions can be listed with --archived flag (experimental).

workflow list flags

workflow list command flags: --archived (bool, optional): Limit output to archived Workflow Executions, experimental; --limit (int, optional): Maximum number of Workflow Executions to display; --page-size (int, optional): Maximum number of Workflow Executions to fetch at a time from server; --query/-q (string, optional): SQL-like Query List Filter.

ListActivitiesAsync lists Standalone Activity Executions matching filter

Use client.ListActivitiesAsync() to list Standalone Activity Executions that match a List Filter query. The result is an IAsyncEnumerable that yields ActivityExecution entries. These APIs return only Standalone Activity Executions; Activities running inside Workflows are not included. The query parameter accepts the same List Filter syntax used for Workflow Visibility, such as "ActivityType = 'ComposeGreeting' AND Status = 'Running'".

CountActivitiesAsync counts Standalone Activity Executions matching filter

Use client.CountActivitiesAsync() to count Standalone Activity Executions that match a List Filter query. This returns the total count of executions (running, completed, failed, etc.) - not the number of queued tasks. It works the same way as counting Workflow Executions. The query parameter accepts the same List Filter syntax used for Workflow Visibility.

ListActivities uses List Filter query syntax

client.ListActivities() accepts a Query field that uses List Filter syntax, the same syntax used for Workflow Visibility. The query field in ListActivitiesOptions takes expressions like "TaskQueue = 'standalone-activity-helloworld'" or "ActivityType = 'Activity' AND Status = 'Running'".

CountActivities returns total count of executions

client.CountActivities() returns the total count of executions (running, completed, failed, etc.) - not the number of queued tasks. It works the same way as counting Workflow Executions.

Visibility APIs work across active and standby clusters

All Visibility APIs can be used against both active and standby Clusters. This enables Temporal UI to work seamlessly for Global Namespaces. Applications making API calls directly to the Temporal Visibility API continue to work even if a Global Namespace is in standby mode, though they might see a lag due to replication delay when querying Workflow Execution state from a standby Cluster.

Give your agent this brain