When you enable data sync on a record type, your source data is cached in Appian.
To keep your synced data up-to-date with the source, we'll automatically sync any data changed by select smart services. If other systems or other smart services are writing to your data source, you can also sync those changes by configuring additional sync options.
However, sometimes record types fail to sync to the source. When this happens, you can use the information in this page and in the error messages found in the Monitor view to resolve issues with sync.
When an error occurs during a sync, the record type will either have a sync status of Failed, Failed and Skipped, or Failed and Retrying. You can find the record type's status by viewing its Sync History.
The type of error that occurs will determine the sync status on your record type, and whether or not the record type is available. It's important to understand which errors cause each status so you can determine how to address them.
If you see a Failed sync status, this means that the sync failed and any references to the record type are currently unavailable. As a result, any queries to the record type will not return data, the record list will be unavailable, and any grids or charts that use the record type may return an error.
A failed sync may also impact queries or components that reference the record type through a record type relationship. For example, suppose a query returns data from the Customer record type, which is related to an Order record type. If the Order record type has a sync status of Failed and the query includes fields from Order, the query will also fail.
Usually the best way to resolve failed syncs is to identify the problem and perform a full sync. When viewing the record type, failed syncs will display with a link to an error message with more details. See causes of sync errors to find methods to resolve common errors.
In other cases, you may see a sync status of Failed and Skipped. This means that a full sync failed, but the record type is still available because it skipped the failed sync and instead uses data from the last successful full sync. As a result, any queries to the record type will succeed. However, since the sync was skipped, the data in your record type may be outdated.
This sync status will only appear if you've configured a record type to skip failed syncs. By default, this setting is enabled on all new record types.
There are some instances where a sync can be automatically retried if an error occurs. In this case, you'll see a sync status of Failed and Retrying.
When the sync is retrying, the sync is still considered in progress and the data for the record type is still available. There are two ways that a retry occurs: retrying the entire sync or only retrying a single batch.
When the entire sync is retried, the sync starts over from the first batch after a delay of a few minutes. A full retry can occur when some intermittent issues occur such as connection timeout with the source system. The retry occurs automatically.
When performing a full sync, the sync will query data in batches. In some cases, there are intermittent errors that can occur that only affect a single batch.
For instance, a record type that uses a web service as the source could have a request time out against the web service during a single batch, even if prior batches succeeded. Batches that fail during a full sync are automatically retried after a brief delay. Specifically, a single batch can be retried twice, and during a full sync, up to 10 total retries can occur. If a single batch fails three times in a row or more than 10 total failures occur, the sync will fail.
Automatic retries that succeed will continue with the remainder of the sync. The Sync History will not display information about failed batches. However, any failure is logged in the application server log to aid with additional troubleshooting.
When an error occurs that causes the sync to fail or skip, an email alert will be sent to system administrators, and any users with Administrator permissions for the record type. The email will contain a summary of the issue and a link to the record type so you can quickly resolve the issue.
Users will only receive email alerts if the sync fails during a scheduled full sync or when you use select smart services to update your source data.
The following sections outline different sync errors and possible resolution steps.
When you enable data sync for your record type and configure your record fields, Appian automatically creates a mapping between the source schema and record type schema.
The source schema includes the names, types, and uniqueness constraints of all the fields in your source. This schema must match the record type's schema in order for Appian to sync the source data.
If a change is made to the source schema without making a corresponding change to the record type, the record type will fail to sync. There are three common causes for a mismatch between the two schemas:
If your record type is backed by a database table or Salesforce, then you can easily remap your record fields to your source fields.
To update the mappings for any of the above scenarios:
To remove a record field and its source field, click the delete icon.
Removing a record field will cause any existing field references to break. To see which objects reference a record field, click next to the record field on the Data Model page of the record type.
If your record type is backed by a web service, then you will need to add the changed field as a new field in your record type. This means that you will also need to find and replace any broken links to the old record field.
To do this:
When data is entered into your source, it's possible to enter values that aren't compatible with data sync. This means that the value in a source field may work fine in your source, but may not be a compatible value for that field in Appian when data sync is enabled.
This most commonly occurs with date fields and date and time fields. Appian has a certain range that all date and date and time values must be within in order for the source data to work with data sync. This range may not be the same range that is accepted by the source; so it's possible that a value can be valid in the source's range but not in Appian's. If the value of a date or date and time field isn't within the range allowed by data sync, the sync will fail.
This specific error message appears when the value of a date and time field in the source is outside of the range of date values that work with data sync. To resolve the error, find the field with the invalid date and time value, update the value so that it is within the valid range, and then resync the record type to the source.
|Field Type||Range||Other Limits|
|Date & Time||Between
||Shouldn't contain the value of
To update the invalid date and time value in the database table:
APNX-3-1100-007: marshal: unsupported timestamp 3000-01-01 00:00:00 +0000 UTC
1 SELECT * FROM `< table name >` WHERE date(< field name >) = `< the invalid value >
To update the invalid date and time value in Salesforce:
APNX-3-1100-007: marshal: unsupported timestamp 3000-01-01 00:00:00 +0000 UTC
When you set up your Salesforce object as the source for your record type, you have to provide login credentials in order to access Salesforce.
If the Salesforce object's credentials are determined to be invalid at the time of the sync, your sync will fail. It could simply be that the password has expired or that the credentials have changed. In order to successfully sync, you need to verify the credentials and re-sync the record type.
To check the credentials and re-sync:
For more information on authentication, credentials, and configuring a Salesforce object, see Salesforce Connected Systems.
With data sync, each record type object can sync up to 2,000,000 rows of data from a selected source.
If you try to sync more than 2,000,000 rows in your record type, the sync will fail and the record type will be unavailable. Record types within 10% of the limit (1,800,000 to 2,000,000 rows) will sync successfully, but a warning will let you know that the record type is approaching or has reached the row limit.
To keep your record type from exceeding the row limit, apply one or more source filters to limit the number of rows synced in Appian.
If the record type is expected to regularly exceed 2,000,000 rows, you may choose to disable data sync.
The Sync Records smart service allows you to specify which records to sync in Appian. You can sync up to 1,000 records at a time.
If you try to sync more than 1,000 records using this smart service, the sync will fail and the record type will be unavailable.
To prevent the smart service from syncing more than 1,000 records at a time, you can create a loop in your process model to execute the Sync Records smart service multiple times.
See Syncing more than 1,000 records for more information.
If you're performing a full sync that takes longer than 4 hours, it's possible that the sync will time out and fail. When the sync fails, the record type will become unavailable and you'll see an alert message that says "The sync failed because it exceeded the 4 hour time limit."
A sync timeout can occur on any record type with data sync enabled, but may be more common on record types that use a web service as the source.
To prevent a sync from timing out, consider:
If you cannot modify the above configurations, or your record type uses a database table as the source, you may choose to disable data sync on your record types that take longer than 4 hours to sync.
When you use a web service as the source of a record type, the web service itself could return an error. For instance, the web service could be temporarily unavailable or the request from Appian may not be structured correctly.
When these errors occur, the Monitor view can display the error received from the web service to help in troubleshooting. However, the source expression must be set up correctly to expose these error messages to the monitor.
In the source expression rule, each batch result must return a list of dictionary, map, or CDT to perform a successful sync; any other result will cause the sync to fail.
However, if the expression rule returns a result of type Integration Error in a batch, the batch will fail and the full details of the integration error will be displayed in the Monitor view for the record sync.
The Integration Error data type returns details on the error that occurred with any integration call. It is returned by default in any integration response using the
error parameter. See below for an example on how to configure the source expression to return the integration error.
Since the integration error typically contains the error received from the web service, it can help troubleshoot issues for the batch that failed.
To provide the integration error in a failed batch, make sure the source expression returns the appropriate integration error.
For example, the following source expression would return the results if the integration succeeds and the integration error if it fails.
1 2 3 4 5 6 7 8 a!localVariables( local!integration: rule!EX_IntegrationResult(batch: ri!batch), if( local!integration.success, local!integration.result.body, /* Returns the result body when the request succeeds */ local!integration.error /* Returns the integration error when the request fails*/ ) )
Check the integration error against common HTTP errors and update the configuration of the integration object to resolve the error. For example, an error code of 401 typically means that the request did not have the correct authentication, so the credentials may need to be updated.
In some cases, it may be necessary to contact the owner of the web service to troubleshoot further.
Sometimes record types fail to sync to the source because of issues that require troubleshooting outside of Appian. When this happens, check the error message for information to help you troubleshoot the issue or contact your system administrator for further assistance.
Here are a few brief explanations of these issues and their possible causes:
|Issue||Error Message||Possible Cause|
|Problem connecting to the source.||
||The source didn't respond, VPN failed, or the API limit has been reached.|
|Problem with the sync server.||
||The disk is full or the disk space is at or near 95% capacity. Alternatively, the sync server may be down.|
|Problem with row size.||
||A source row exceeds 1 MB.|
|Problem with resource use.||Generic error:
||Too much competition for resources between syncs and other processes.|
|Problem with invalid batches.||
||The sync expects that the data changes with each batch, but the first two batches returned the same data.|
|Problem with invalid primary key data.||
||The data source has multiple records that have the same primary key value.|
There are some cases when you may want to disable data sync, like when your record type is expected to exceed the row limit, or if your syncs take longer than 4 hours.
If you choose to disable data sync, you will need to update the source configuration of your record type. This will create new record fields with new UUIDs, so you will also need to update any existing references to your record fields with the new record field references.
To disable data sync:
To find and replace existing field references in your environment:
Paste the string into the search box under ALL OBJECTS.
You can search for multiple strings at once by separating each string with a space.
Every object that references the string will appear in your search results. Once you have located all the references in your objects, update the field references. For updating field references in interfaces, we recommend updating the references in Expression Mode.
On This Page