Verifiable incident

Missing Metadata in Salesforce

Minor Resolved View vendor source →

Verifiable experienced a minor incident on October 20, 2025 affecting Salesforce Package, lasting 6h 28m. The incident has been resolved; the full update timeline is below.

Started
Oct 20, 2025, 05:02 PM UTC
Resolved
Oct 20, 2025, 11:30 PM UTC
Duration
6h 28m
Detected by Pingoru
Oct 20, 2025, 05:02 PM UTC

Affected components

Salesforce Package

Update timeline

  1. investigating Oct 20, 2025, 03:03 PM UTC

    We are aware that some customers are experiencing missing metadata (such as provider types) in Salesforce. Our team is actively investigating the issue and will provide an update as soon as more information becomes available.

  2. identified Oct 20, 2025, 06:32 PM UTC

    We have identified the issue and are working on a solution to restore the missing metadata for affected organizations. The metadata is refreshed through a background job that syncs values from our platform to Salesforce to populate picklists. Due to the ongoing issues with our cloud provider, this job inadvertently cleared those cached values. The affected metadata is redundant and can be safely restored without any impact on customer data. We will share further updates as more information becomes available.

  3. identified Oct 20, 2025, 06:43 PM UTC

    We are working to populate the cache for the missing metadata for affected organizations. A fix is currently being validated, and deployment will begin once we are confident it can be applied safely. We will share another update as soon as more information becomes available.

  4. identified Oct 20, 2025, 09:42 PM UTC

    The fix to repopulate the metadata cache has been validated and is now being deployed to all affected organizations. We will provide another update once all organizations have been successfully updated.

  5. monitoring Oct 20, 2025, 10:58 PM UTC

    The fix has been deployed to most affected organizations, and we’re seeing improved performance. We’ll continue to monitor to ensure full recovery across all affected organizations.

  6. resolved Oct 21, 2025, 12:15 PM UTC

    This incident has been resolved.