Temporal
Durable workflow orchestration component in the Foundation layer.
Component Category
Workflows and automation / durable workflows
Component Description
Temporal is a workflow orchestration platform built for long-running, stateful, and fault-tolerant processes.
Why It Is Used
In BullSequana AI Foundation, Temporal is used when workflows must be durable, resumable, and reliable across failures, retries, and long execution times.
Learn More
What runs on Temporal
The BSQAI API runs its long-running work as Temporal workflows. Each kind of work has its own worker deployment in the BSQAI API namespace:
| Worker | Workflows |
|---|---|
tenant-lifecycle-worker | Creating, changing, and deleting tenants through the BSQAI Tenant Operator |
keycloak-sync-worker | Synchronizing Keycloak identities into OpenFGA authorization relationships on a schedule |
mcp-reconcile-worker | Reconciling Managed MCP Servers |
file-rag-worker | File ingestion and indexing |
rag-reconcile-worker | Repairing upload and reindex states that a workflow left stale, on a schedule |
reindex-worker | Reindexing files into a new vector index |
skill-publication-worker | Publishing skills |
deep-research-worker | Deep Research runs |
data-connectors-worker | Managed-ingestion connectors and schedules |
Temporal stores workflow history and schedules. These platform workflows are separate from user-authored Kubeflow Pipelines and Argo Workflows.
Managed-ingestion orchestration
The BSQAI API connector worker owns the workflows and schedules used by Studio data ingestion. Temporal coordinates Kubernetes coordinator Jobs; source and destination connector containers perform the data transfer. Workflow history carries execution references, not record batches or plaintext credentials. Retry and cancellation do not roll back destination writes. Customers register connector images and schemas, not Temporal workflow code.
Deployment notes
Temporal deploys into the temporal namespace at sync wave 2 in the coreai tier. It stores workflow state and workflow search (visibility) in two CNPG PostgreSQL databases, temporal and temporal_visibility, so Temporal has no volume of its own.
The Temporal UI is behind an Envoy Gateway security policy. It signs users in with the temporal Keycloak client and admits only members of the platform-administrators realm group. Everyone else is refused.
BullSequana AI runs Temporal server 1.32. Temporal upgrades its schema one minor release at a time. When a platform upgrade skips Temporal minor releases, the platform runs each intermediate schema migration against the databases before it deploys the new server. See Upgrade Temporal to 1.32 to check that migration, run it by hand, or restore from a backup.
The [database] num_history_shards value is fixed when Temporal first starts. Keep it unchanged on an existing installation.
Interacts With
BSQAI API, whose workers run tenant lifecycle, authorization sync, Managed MCP Server, file, retrieval, skill, Deep Research, and managed-ingestion workflows.Kubernetes, which executes ingestion coordinator Jobs and customer connector containers.PostgreSQL, which stores Temporal persistence and visibility data.Keycloak, which signs platform administrators in to the Temporal web UI.OpenFGA, which the tenant lifecycle and Keycloak sync workflows update with tenant and membership relationships.PrometheusandGrafana, through service monitors and metrics collection.