Understanding Multi-Tenant Processing

Key Takeaways

  • Tenant identity and authorization scope distinguish records, configurations, and workloads on shared services.

  • A scheduled time can enqueue work. Check actual task start, completion and downstream results.

  • Workflow and API gateway limits meter distinct workloads and have different effects.

  • Confirm the tenant, presented actor, and process before comparing counts or resolving delays.

Last updated: November 2026

Identify the correct isolation boundary

A multi-tenant software service can operate common infrastructure while serving multiple organizations. Each tenant has its own logical identity and records. SailPoint describes using a unique tenant identifier in workload handling, access controls, and partitioning. It describes both separated and pooled data stores depending on the feature. A deployment therefore needs tenant-aware controls even when a database or runtime is shared. Do not infer the physical database layout of a specific feature just because one part of the platform is pooled.

Production and staging can be distinct tenants for the same organization. A tenant's identity profile, workflow, client registration or source record belongs to its own tenant context. Confirm the tenant host, environment and relevant object identifier even when names look identical. A delegated administrative role or a data segment limits what a caller may do or see within the applicable tenant. It serves a different purpose from the boundary between tenants. Configuration Hub can move supported configuration through an explicit deployment path. A similarly named role or managed source in another tenant does not turn that environment into the original one.

MechanismWhat it scopesExample evidence
Tenant contextService instance, organization identities, configuration and workloadsOrganization ID or name and the expected tenant host
Role and record controlsOperator abilities and permitted objects inside that tenantEffective role, segment and allowed/denied comparison
Identity processing scheduleWhen applicable identities are queued for further processingJob queue and actual execution records, applicable eligibility and tenant time settings
API gateway rate limitIncoming API requests for a client and API version under the default ruleActual response and Retry-After, request timing and version
Workflow execution safeguardsDaily tenant pressure and individual workflow execution or loop activityTenant and workflow usage widgets, warnings and execution history
VA cluster request pathWork directed to a configured source's selected clusterSource association, member health and actual connector result

Work a case involving two tenants

A tenant administrator compares production and staging and finds that a status update expected shortly after a scheduled time appears only in staging. Verify the intended production tenant and its configured time zone first. The platform queues scheduled identity processing at the documented times for eligible identities. Other pending or in-progress work can delay the job start. The scheduled time therefore describes submission and does not establish completed processing or access fulfillment. Inspect the production job and affected record, and check whether the identity meets the applicable processing conditions. Then verify the expected identity or target result, independent of the equivalent staging job. If the record depends on Search, account also for its indexing and visibility.

An asynchronous API acceptance similarly establishes that a request has entered the process. Depending on the documented operation, use its status or the relevant activity record and compare the actual result. When a VA-based source is involved, inspect the source's selected cluster and target path. A backlog in that path and a tenant job waiting for execution are two distinct explanations. A safe test or retry should be scoped to the actual failed stage.

Interpret a performance limit by the correct counter

The current API gateway default is counted per client ID and API version. This limit is separate from the tenant's workflow execution and individual workflow limits. SailPoint documents a tenant-wide daily workflow count that excludes loop executions and can lead to throttled execution for the rest of the day. The per-workflow high-execution count includes loops and can block the affected workflow's remaining executions after the documented threshold. Use the tenant and individual execution widgets to identify which behavior applies. A resource call returning a gateway rate response has different evidence from a warning about workflow executions.

If a batch rollout brings one workflow close to its limit, measure the number of triggering events and expected loop iterations, and verify the execution results before increasing load. Concentrate on the documented counter, tenant and time window. Investigate provider status separately if there is a regional incident or if unrelated services are affected.

See the tenant partitioning description, identity processing, workflow execution limits, gateway limits, and Configuration Hub scope.

Test Your Knowledge

The production identity processing schedule time passed, and staging updated the analogous test identity. What should the engineer check before assuming production processed the record?

A

Whether the staging workflow diagram has the same labels.

B

The gateway quota of a separate API client.

C

Whether the two tenants show the same public service status.

D

Production tenant and timing, the affected identity’s eligibility and actual queued job and result.

Test Your Knowledge

An individual workflow’s high-execution warning appears after a change added many loop iterations. Which measure most directly explains that warning?

A

The number of OAuth access tokens issued for the tenant.

B

The count of that workflow’s executions plus loop executions under its individual guardrail.

C

The number of registered VA members at the recovery site.

D

The number of public identity pages returned for a caller.

Sections you finish are checked off in the contents.