Error 00004: System.LimitException: Apex CPU time limit exceeded

Cause

This error is due to a Salesforce limitation on the time it's taking the data to sync to the device. The following are the current estimated limits on the volume of data that you can sync to an individual mobile user. They are estimates because the actual limit is a function of time, so there are many variables including speed of connection, number of forms being sent the device, etc. In the below tables, Total Selected Fields is the sum of all Selected fields in the Drill-down hierarchies of Jobs assigned or a mobile user.

Versions below TaroWorks 4.8:

Total Fields*	Total Records
1	10,000
5	7,000
10	4,000
15	2,000
20	1,000

Starting in TaroWorks 4.8:

1.5 GB RAM Device

Total Fields*	Total Records
20	40,000
40	32,000
100	8,000

 

1.0 GB RAM Device

Total Fields*	Total Records
20	24,000
40	16,000
100	4,000

 

* This is the total number Selected Fields in the drill-down hierarchies across all Jobs assigned to a Mobile User.

Solution

There are two approaches to resolving this issue: reduce the data that needs to be synced to the device, or improve the mobile user's connection so that it syncs faster. Usually the second is not possible so here are your options for reducing data that is being synced to the device:

1. If you are on a version below TaroWorks 4.8, please upgrade to 4.8 to increase the volumes that you can sync to the device.

2. For versions below TaroWorks 4.8, you can do piecemeal mobile record assignment. For example, if you're assigning 10 Village records to a mobile user, you can assign 5, have the mobile user sync, assign the remaining 5 and have the mobile user sync again. However, if new villages are going to be created and assigned to the mobile user frequently, this is not a sustainable solution.

3. Use drill-down hierarchy filters to narrow down the data synced to the device to only exactly what the mobile user needs.

4. Reduce the number of detail fields required by each record in your Jobs' drill-down hierarchies to narrow down the data synced to the device to only exactly what the mobile user needs.
   

5. Use Assigning Jobs to Groups to narrow down the Jobs to only exactly the Jobs the mobile user needs.

6. Re-evaluate your mobile record assignment level in your object structure. If you're assigning records at too high of a level, causing a high volume of superfluous child records to be synced to the device, choose a lower level (ideally still above the level at which new records are generated in the field) to more exactly send only what the mobile user needs.

7. Disable Offline Jobs Integration, which allows you to create a record in one Job and use it in the drill-down hierarchy of another without syncing. While a powerful feature, it is only recommended when syncing small data volumes.

 Note: If an individual mobile user is experiencing longer or slower sync times than other mobile users, check to see whether Salesforce debug logs are set up for that user, which would cause additional processing. Disabling those logs would reduce the processing required for that user upon syncing.