Project automation succeeded, but a CRM field didn't change

Last updated: October 2, 2026

Applies to: Super Admins, Creators, and Integrators, with Salesforce or HubSpot connected

Project automations are available when they're turned on for your organization. If you don't see an Automations tab on your projects, contact your OnRamp team.

The log shows a check mark for the update, but a Salesforce field or HubSpot property didn't get the value you expected. The row's Payload shows which fields OnRamp left out or shortened, and why.

Why it happens

An Update Salesforce field or Update Hubspot field action can succeed even when OnRamp leaves out a mapped field or shortens its value. The rest of the update still goes through, so the row gets a check mark. Its Payload lists those fields by their CRM API name, not their label:

  • skipped_fields: OnRamp didn't send the field, so the CRM kept its old value. The reason is not in the CRM field list when OnRamp couldn't find the field on the CRM object. It's mapped value is empty when the OnRamp value had nothing in it.
  • truncated_fields: the value was longer than the CRM field allows. OnRamp sent the first max_length characters, and original_length is the full length.

Fix it

  1. In the project's Logs, find the Update Salesforce Field or Update Hubspot Field row for the event.
  2. In Payload, select View, and find your field in skipped_fields or truncated_fields.
  3. On the Automations tab, select the automation.
  4. Select its Update Salesforce field or Update Hubspot field step.
  5. Fix the field based on what you found:
    • not in the CRM field list: in Salesforce or HubSpot, check that the field still exists on that object. Then select the refresh button next to Salesforce Object Entity or Hubspot Object Entity, and select the field again under Update this field.
    • mapped value is empty: fill in the value it's mapped from, such as a data field on the project's Data Fields tab. Or select a different value under With this data. On a Subtask completed trigger, only subtasks answered before the triggering one have a value.
    • truncated_fields: in Salesforce or HubSpot, let the field hold a longer value. Or select a shorter value under With this data.
  6. If you changed the mapping, select Save.
  7. Repeat the event on the project, and then select Refresh in Logs.

If your field is in neither list, find it in the fields list under record. That's the value OnRamp sent, to the record whose id is under record. Check that record in Salesforce or HubSpot.

Still stuck?

Contact support with the project's name and link, the automation's trigger and action, the field's API name, the row's Timestamp, and the text from Payload.

Related articles