UiPath Status

Resolved: The issue has been fully resolved and service is back to operational.

Monitoring: The stale subscriptions have been cleaned up and message delivery has been restored. Robot allocation changes are now propagating to Orchestrator as expected. We are actively monitoring the system to ensure stability and confirm no further throttling occurs.

Identified: We identified an issue where robot allocations made at the tenant level were not being reflected in Orchestrator. The root cause was traced to messages throttling caused by exceeded storage quotas. Stale duplicate subscriptions with no active consumers had accumulated unread messages, exhausting the storage limit and blocking new message delivery.

Resolved: The issue has been fully resolved and service is back to operational.

Monitoring: The stale subscriptions have been cleaned up and message delivery has been restored. Robot allocation changes are now propagating to Orchestrator as expected. We are actively monitoring the system to ensure stability and confirm no further throttling occurs.

Identified: We identified an issue where robot allocations made at the tenant level were not being reflected in Orchestrator. The root cause was traced to messages throttling caused by exceeded storage quotas. Stale duplicate subscriptions with no active consumers had accumulated unread messages, exhausting the storage limit and blocking new message delivery.

Resolved: The issue has been fully resolved and service is back to operational.

Monitoring: The stale subscriptions have been cleaned up and message delivery has been restored. Robot allocation changes are now propagating to Orchestrator as expected. We are actively monitoring the system to ensure stability and confirm no further throttling occurs.

Identified: We identified an issue where robot allocations made at the tenant level were not being reflected in Orchestrator. The root cause was traced to messages throttling caused by exceeded storage quotas. Stale duplicate subscriptions with no active consumers had accumulated unread messages, exhausting the storage limit and blocking new message delivery.

Resolved: The issue has been fully resolved and service is back to operational.

Monitoring: The stale subscriptions have been cleaned up and message delivery has been restored. Robot allocation changes are now propagating to Orchestrator as expected. We are actively monitoring the system to ensure stability and confirm no further throttling occurs.

Identified: We identified an issue where robot allocations made at the tenant level were not being reflected in Orchestrator. The root cause was traced to messages throttling caused by exceeded storage quotas. Stale duplicate subscriptions with no active consumers had accumulated unread messages, exhausting the storage limit and blocking new message delivery.

Resolved: The issue has been fully resolved and service is back to operational.

Monitoring: The stale subscriptions have been cleaned up and message delivery has been restored. Robot allocation changes are now propagating to Orchestrator as expected. We are actively monitoring the system to ensure stability and confirm no further throttling occurs.

Identified: We identified an issue where robot allocations made at the tenant level were not being reflected in Orchestrator. The root cause was traced to messages throttling caused by exceeded storage quotas. Stale duplicate subscriptions with no active consumers had accumulated unread messages, exhausting the storage limit and blocking new message delivery.

Resolved: The issue has been fully resolved and service is back to operational.

Monitoring: The stale subscriptions have been cleaned up and message delivery has been restored. Robot allocation changes are now propagating to Orchestrator as expected. We are actively monitoring the system to ensure stability and confirm no further throttling occurs.

Identified: We identified an issue where robot allocations made at the tenant level were not being reflected in Orchestrator. The root cause was traced to messages throttling caused by exceeded storage quotas. Stale duplicate subscriptions with no active consumers had accumulated unread messages, exhausting the storage limit and blocking new message delivery.