---
schema_version: "1"
id: 3db3ea2a91ab2698c929e03fefae67f2cc9e4736c1bd3077ddf91e85ee1a8c89
title: Sales and Service Cloud Activity Field Validation and Error Handling
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/mktg/264-0-0/mc_jb_sales_service_activity_validation_error.md
canonical_url: https://help.salesforce.com/s/articleView?id=mktg.mc_jb_sales_service_activity_validation_error.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: bcbd8846ba3151e0f0ca6105079de63c70cc3a27e7c6cc751ed7910727e25564
description: Review the requirements for Sales and Service Cloud activity field values. Incorrect field values can cause activity errors in Journey Builder.
products:
  - Marketing
  - Marketing Cloud Engagement
release: "264"
---
# Sales and Service Cloud Activity Field Validation and Error Handling

Review the requirements for Sales and Service Cloud activity field values. Incorrect field values can cause activity errors in Journey Builder.

## Field Validation

Text fields don’t have a specific format, but picklist and boolean fields only allow you to choose from a list. Other field types require a specific format. Here are the field types with built-in validation requirements that prevent configuration of the activity until they’re resolved.

Email

The email field value must follow the common format, name@domain.com.

Date

The date field is based on your account's time zone. There are four valid date formats.

 
| Format | Example |
| --- | --- |
| YYYY-MM-DD | 2019-05-31 |
| YYYY-MM-DD hh:mm:ss | 2019-05-31 15:00:00 |
| YYYY-MM-DDThh:mm:ssZ | 2019-05-31T15:00:00Z |
| YYYY-MM-DDThh:mm:ss.sssZ | 2019-05-31T15:00:00.123Z |

DateTime

The DateTime is based on your account's time zone. There are three valid formats.

 
| Format | Example |
| --- | --- |
| YYYY-MM-DD hh:mm:ss | 2019-05-31 15:00:00 |
| YYYY-MM-DDThh:mm:ssZ | 2019-05-31T15:00:00Z |
| YYYY-MM-DDThh:mm:ss.sssZ | 2019-05-31T15:00:00.123Z |

Currency

The currency field accepts numbers only and a maximum of one decimal point. A maximum of two digits can follow the decimal point. Don’t include any digit group separators.

 
| Example Valid Value | Example Invalid Value |
| --- | --- |
| 200 | $200 |
| 1520.99 | 1520.990 |
| 14000.1 | 14,000 |

Integer

The integer accepts only numbers. Don’t include decimal points or digit group separators.

 
| Example Valid Value | Example Invalid Value |
| --- | --- |
| 1 | 1.0 |
| 1523810 | 1,523,810 |

Double

The double field accepts only numbers and a maximum of one decimal point. Don’t include digit group separators.

 
| Example Valid Value | Example Invalid Value |
| --- | --- |
| 1340.15 | 1,340.15 |
| 56320.00 | 56,320 |

## Errors

Review the common errors that occur for Sales and Service Cloud activities.

Design-Time Errors

Here are some of the common errors that can result from incorrect activity configuration.

- An invalid or broken integration: Cross-cloud activities require a complete and functioning integration with Sales Cloud and Service Cloud.
- Incorrect permissions: There are permissions in place that allow a user to create integration activities. If those permissions aren’t set correctly, the user can’t configure a new activity.

Runtime Errors

Runtime errors occur when a contact enters an activity in a running journey. In some situations, these contacts aren’t processed correctly. It’s difficult to detect these errors because Sales and Service Cloud activities in Journey Builder use soft errors. A soft error doesn’t stop the contact from continuing through the journey. Here are some common runtime errors.

- Missing or deleted objects: When an object referenced in the activity is no longer available after the journey is activated, the activity can’t complete its function.
- [Row-locking](https://help.salesforce.com/s/articleView?id=000387767&type=1&language=en_US): Some objects, especially CampaignMember, can time out when a contact record locks and the operation stalls.
- Failed Lookups: Sales and Service Cloud activities include options for how to proceed when a lookup fails to find a contact record. However, it’s possible that the lookup request can fail during processing. When the request fails, the activity errors, but the contact continues in the journey.
- Required Fields: If the selected attribute for a required field is empty, the activity errors.