Flxbl Toolkit Outage History

Started Sep 17, 2026, 01:33 PM UTC· resolved Sep 17, 2026, 01:49 PM UTC

1. investigating Sep 17, 2026, 01:33 PM UTC

   A tenant is currently experiencing an outage We are currently investigating

2. resolved Sep 17, 2026, 01:49 PM UTC

   Issue has been resolved

3. resolved Sep 17, 2026, 01:49 PM UTC

   Issue has been resolved

Read the full incident report →

Started Sep 17, 2026, 03:43 AM UTC· resolved Sep 17, 2026, 05:49 AM UTC

1. investigating Sep 17, 2026, 03:43 AM UTC

   Our daily backup job is not functioning We are currently looking into the issue

2. identified Sep 17, 2026, 04:07 AM UTC

   Root cause found, we're rolling out a fix

3. resolved Sep 17, 2026, 05:48 AM UTC

   All instances are patched, and backup is now executed

4. resolved Sep 17, 2026, 05:49 AM UTC

   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

5. resolved Sep 17, 2026, 05:49 AM UTC

   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

Read the full incident report →

Started Sep 14, 2026, 08:55 PM UTC· resolved Sep 15, 2026, 09:41 AM UTC

1. identified Sep 14, 2026, 08:55 PM UTC

   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.

2. monitoring Sep 15, 2026, 06:33 AM UTC

   We are applying the fix to tenants, We will update when the rollout is completed

3. resolved Sep 15, 2026, 09:41 AM UTC

   All instances are patched

4. resolved Sep 15, 2026, 09:41 AM UTC

   All instances are patched

Read the full incident report →

Started Aug 26, 2026, 12:58 PM UTC· resolved Aug 27, 2026, 05:07 AM UTC

1. identified Aug 26, 2026, 12:58 PM UTC

   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.

2. resolved Aug 27, 2026, 05:07 AM UTC

   Fix is now rolling out to all tenants

3. resolved Aug 27, 2026, 05:07 AM UTC

   Fix is now rolling out to all tenants

Read the full incident report →

Started Jul 27, 2026, 11:44 AM UTC· resolved Jul 27, 2026, 01:41 PM UTC

1. identified Jul 27, 2026, 11:44 AM UTC

   Users will be unable to sync or deploy using desktop app

2. resolved Jul 27, 2026, 01:41 PM UTC

   Please update to the latest version of the app

Read the full incident report →

Started Jul 25, 2026, 01:33 AM UTC· resolved Jul 25, 2026, 02:48 AM UTC

1. identified Jul 25, 2026, 01:33 AM UTC

   Codev Desktop App is crashing against instances which have been updated to v51.40.0

2. resolved Jul 25, 2026, 02:48 AM UTC

   Please update your codev desktop client to 1.18.2 which resolves this issue

Read the full incident report →