Workato Trigger Behavior with Null Salesforce Date Fields

[San]

In my recipe, I’m using a trigger condition to pick new or updated Contracts from Salesforce where:

contract_end_date.to_date > yesterday

If one of the records has a blank or null Contract End Date, how does the Salesforce connector behave? Will it still evaluate and process the remaining records that meet the trigger condition, or will the empty date cause the entire batch to fail? 

[San]

Ah, now I am able to upload. Please find below screenshot.

 

[rajeshjanapati]

actually your error is, formula can't be applied to NULL values, for that simply you can add another trigger condition like CONTRACT_END_DATE.isPresent as shown in image.

You can implement this in 2 approaches,

1. as you mentioned about trigger conditions

2. using SOQL WHERE clause

Please check the images for both approaches:

Hope you got my point?

Thanks,

J Rajesh Kumar.

[San]

Yes, I was able to resolve the issue by adding a null check in my condition. Before applying this fix, the recipe was not processing records even when they met the criteria. Ideally, the connector should throw an error for only the problematic record and continue processing the remaining valid records, but in this case the entire job stopped due to the null value.

Isn't it connector need to handle this smartly ?

Thank You

San

[rajeshjanapati]

Have you tried with Query?

if not, Please try with SOQL query once and let me know, if you still face an error.

[shivakumara]

Hi @San ,
Here is my understanding on the ask
Why it can affect other jobs

• When multiple jobs share the same object and trigger condition, they compete for the same evaluation logic.
• If one job encounters an error (e.g., missing field value, invalid condition), the system might:
  • Fail the evaluation for that job only (ideal scenario).
  • Or, in some implementations, block the trigger evaluation for all jobs using that condition until the error is resolved.

  • Concurrency Behavior: When concurrency is set to 3, the recipe does not display an error message upfront like it does when concurrency is 1. If you want the trigger to validate and show errors before processing, that’s not recommended—but you can always add a condition check after the recipe is triggered.

  • Field Type Impact: For Date/DateTime fields, missing values behave differently in your case, fields are not mandatory. Comparisons like “less than” or “greater than” on empty dates will show an error even though recipe is running, unlike numeric fields (e.g., amount, ID) where such conditions typically skip the job.
    
    

  • Trigger Conditions:
    Add the condition shown in the last image to prevent error messages in the recipe.
  • The logic checks if the date field exists:
    • If present, it uses the actual date field.
    • If not, it assigns a default value (in this case, now.to_date() - 1.days) for comparison against your date condition.
      
      Concurrency=1Concurrency set to more than 1No errors in case concurrency set more than 1Skipping job when I set the Amount as trigger condition with not sending any values
      

     Skipping job when we set up above condition
Thanks and Regards,
Shivakumara K A