Eloqua Bulk API Connector > Troubleshooting > Troubleshooting Synchronization task and mapping task
  

Troubleshooting Synchronization task and mapping task

When you run an Eloqua Bulk API synchronization task or mapping task, the Secure Agent does not convert the $LastRunTime variable based on the UTC time zone you specify in the Time Zone Offset field in the connection properties.
To solve this issue, you must add the filterWithGivenUTCTimeZone property and set the value as true in the pmrdtm.cfg and tomcat.cfg files.
To set the value of the filterWithGivenUTCTimeZone property, perform the following steps:
  1. 1In Administrator, select Runtime Environments.
    2. The Runtime Environments page appears.
  2. 2Select the Secure Agent for which you want to set the filterWithGivenUTCTimeZone property from the list of available Secure Agents.
  3. 3In the upper-right corner, click Edit.
  4. 4Select System Configuration Details in the Custom Configuration Details section.
  5. 5Select the Service as Data Integration Server and Type as DTM.
  6. 6Add filterWithGivenUTCTimeZone in the Name field and set the Value as true.
  7. 7Click + icon to add another custom configuration property.
  8. 8Select the Service as Data Integration Server and Type as Tomcat.
  9. 9Add filterWithGivenUTCTimeZone in the Name field and set the Value as true.
    10. The following image shows the Custom Configuration Details section:
  10. 10Restart the Secure Agent.
  11. 11In the Eloqua Bulk API connection, set the Time Zone Offset property to Eloqua supported time zone.
  12. 12Click Save to save the connection.
When you set the filterWithGivenUTCTimeZone property to true and run a task, the Secure Agent considers the UTC time zone you specify in the Time Zone Offset field regardless of whether you use a normal filter or filter with $LastRuntime variable.
When you set the filterWithGivenUTCTimeZone property to false and use normal filter in a synchronization task, the Secure Agent does not consider the UTC time zone you specify in the Time Zone Offset field. The Secure Agent considers the UTC time zone only if you use a filter with $LastRuntime variable.
When you set the filterWithGivenUTCTimeZone property to false and run a mapping task, the Secure Agent does not consider the UTC time zone you specify in the Time Zone Offset field regardless of whether you use a normal filter or filter with $LastRuntime variable.