pingoru pingoru Flxbl had 6 outages in the last 2 years totaling 34h 28m of downtime, averaging 0.2 incidents per month.
There were 6 Flxbl outages since July 25, 2026 totaling 34h 28m of downtime. Each is summarised below. Incident details, duration, and resolution information.
Status: Investigating A tenant is currently experiencing an outage We are currently investigating
Status: Resolved Issue has been resolved
Status: Investigating Our daily backup job is not functioning We are currently looking into the issue Affected components sfp server (flxbl managed instances) (Degraded performance)
Status: Identified Root cause found, we're rolling out a fix Affected components sfp server (flxbl managed instances) (Degraded performance)
Status: Resolved All instances are patched, and backup is now executed Affected components sfp server (flxbl managed instances) (Operational)
Status: Resolved Third Party Provider's deprecation to artifact repository was not observed by us, which resulted in scripts to fetch the required tools. We have corrected the same and strenthened our monitoring of notifications Affected components sfp server (flxbl managed instances) (Operational)
Status: Identified Installing a source package that applies layout assignments or search layouts from mutators/*.yml can switch off unrelated settings on the target object, such as Allow Activities, Allow Reports and Allow in Chatter Groups, and clear the object description. sfp cli 51.6.0 and later are affected, including deployments run through codev. Profile-only assignments and unlocked package installs are not. We have identified the cause and a fix is in review. Until it ships, review those objects after each install and re-enable any settings that were switched off. We will post here when the fix is released. Affected components sfp server (flxbl managed instances) (Degraded performance) sfp cli (Degraded performance)
Status: Monitoring We are applying the fix to tenants, We will update when the rollout is completed Affected components sfp server (flxbl managed instances) (Degraded performance) sfp cli (Degraded performance)
Status: Resolved All instances are patched Affected components sfp server (flxbl managed instances) (Operational) sfp cli (Operational)
Status: Identified When a Salesforce org loses access — for example if its stored refresh token expires, or the connection is revoked — a stale lock can be left on the corresponding environment. Releases and other jobs targeting that environment then queue behind that lock instead of failing, and can stay blocked for up to two hours. If you see jobs waiting on an environment lock, deactivate the affected environment. That stops new work being dispatched to it and clears the blockage. Reactivate it once the org has been re-authenticated. A fix is in progress: the lock will be released when the step after acquisition fails, and the wait will be bounded so jobs fail fast rather than queueing indefinitely.
Status: Resolved Fix is now rolling out to all tenants
Status: Identified Users will be unable to sync or deploy using desktop app Affected components codev desktop app (Degraded performance)
Status: Resolved Please update to the latest version of the app Affected components codev desktop app (Operational)
Status: Identified Codev Desktop App is crashing against instances which have been updated to v51.40.0
Status: Resolved Please update your codev desktop client to 1.18.2 which resolves this issue