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 all systems are operating normally.

Monitoring: The database issue impacting IXP and Communication Mining has been resolved, and services are recovering normally. Our team is monitoring the systems closely to ensure continued stability.

Investigating: We are investigating an issue impacting IXP and Communication Mining caused by a database outage. Our team is actively working to restore service and will provide updates as they become available.

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.