Skip to main content

Why Can't Weflow Update a Record It Didn't Create?

Why Weflow can log the first email or meeting on a Salesforce record but not update it later, and the integration user access that fixes it.

If Weflow logs the first email or meeting on a Salesforce record but cannot update it afterwards, the Weflow integration user is missing access to records it does not own.

A meeting that moves or is cancelled stays in Salesforce exactly as it was first logged, and an AI summary reaches some records and not others.

Example: A summary written to an opportunity succeeds, and the same summary written to an account fails with an insufficient access error. Nobody sees an error in Weflow as the summary still exists in the Weflow recording, and the gap shows only when someone asks why some meetings have summaries and others do not.

Note: Weflow never needs Modify All Data. It works with a least-privilege permission set, and the broadest access it asks for applies only when your sharing model is Private.

Why Weflow can't update a record it didn't create

Cause

How to check

Fix

Private org-wide defaults

Sharing Settings, Default Access

Modify All Records on the objects

Private activity sharing

Default Access for Activity

Controlled by Parent, or a higher role

Integration user's role too low

The user's Role field

A role high in the hierarchy

No edit access on Event fields

Permission set, Object Settings, Events

Edit on the fields Weflow updates

Check the org-wide defaults for the Weflow integration user

When your Salesforce org-wide defaults are Private, the integration user only sees and edits records it owns. With Read, Edit and View All alone, it can create the first event or email on a record it does not own, and cannot update it afterwards.

Give the integration user Modify All Records on Account, Opportunity, Contact and Lead.

Security teams often resist Modify All Records because it includes delete. Weflow never deletes an opportunity: it deletes only an event it logged incorrectly, for example when a meeting is cancelled.

Check activity sharing for events Weflow logged

In Salesforce, activities have their own sharing setting. When activity sharing is Private, Modify All Records on the parent Account or Opportunity does not give the integration user edit access to an Event, so it cannot update attendees, times or cancellations.

There are two fixes:

  • Controlled by Parent: set the default access for activities to Controlled by Parent, so access to an event follows access to its record. This is the simpler fix.

  • A higher role: give the integration user a role above the owners of the events it logs.

Check the Weflow integration user's role

A role is not required for the integration user, but Weflow recommends one high in the role hierarchy. An activity the integration user creates is handed to a normal user as its owner.

When that owner sits higher in the hierarchy than the integration user, the integration user can lose the right to update it, so a logged meeting that later changes stays as it was.

Check edit access on the Event fields Weflow updates

Creating an event and editing it are separate rights, down to the field. A permission set that lets the integration user insert events can still block every later change.

The Activity Capture logs then show the updates failing, while new events keep appearing in Salesforce.

  1. In Salesforce, open the Weflow permission set assigned to the integration user.

  2. Go to Object Settings > Events.

  3. Grant Read and Edit on the fields Weflow updates, such as Name (WhoId), Related To (WhatId) and Accepted Event Invitee IDs, or on every Event field. Granting every field is safe: Weflow writes only the fields it uses.

  4. Save the permission set.

A sync-back for the day then re-applies the missed updates, and the events line up within a minute.

Frequently asked questions about Weflow record updates

Why does Weflow need to delete events?

When a meeting is cancelled in the calendar, Weflow removes the event it logged, so Salesforce matches the calendar. It deletes only events it logged, never opportunities or other records.

Are updates that failed applied later?

Yes, once the access is fixed. A sync-back for the affected day re-applies the missed updates.

Where do I see activity that failed to log or update?

Admins see skipped and errored emails and meetings in the Activity Capture capture health metrics for a chosen period, with a CSV download.

Did this answer your question?