topic Re: Workato Trigger Behavior with Null Salesforce Date Fields in Workato Pros Discussion Board

Workato Trigger Behavior with Null Salesforce Date Fields

San — Thu, 20 Nov 2025 09:26:58 GMT

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?

Re: Workato Trigger Behavior with Null Salesforce Date Fields

rajeshjanapati — Thu, 20 Nov 2025 10:19:25 GMT

Hi @San,

Here’s how the Salesforce connector will behave in this scenario:

A null Contract_End_Date will not break the batch.
Workato evaluates the trigger condition for each record individually.
If Contract_End_Date is null, it simply doesn’t meet the condition of Contract_End_Date.to_date > yesterday, so Workato skips that record.
The remaining records that match the condition will be processed normally.
If you also want to pick up records where the Contract_End_Date is blank, you can update your condition to include null values in WHERE clause:

Contract_End_Date > YESTERDAY OR Contract_End_Date = null

This way, your recipe will fetch both records with recent end dates and those with an empty end date field.

Feel free to share more details if you need help refining the logic!

Thanks & Regards,

J Rajesh Kumar.

Re: Workato Trigger Behavior with Null Salesforce Date Fields

San — Thu, 20 Nov 2025 10:58:54 GMT

Thank you for the reply, I am also expecting to skip that record and process remaining records that match the condition. But instead I see a below error at recipe and stopped processing any records.

Thank You

San

Re: Workato Trigger Behavior with Null Salesforce Date Fields

rajeshjanapati — Thu, 20 Nov 2025 12:42:28 GMT

Will you please share the screenshot of the Trigger configuration with WHERE condition.

Thanks,

J Rajesh Kumar.

Re: Workato Trigger Behavior with Null Salesforce Date Fields

San — Thu, 20 Nov 2025 13:08:27 GMT

Weird, above I have attached the screenshot but now I am getting don't have permission to upload the screenshot.

Below is my trigger condition:

New/updated Contract in Salesforce
IF Contract End DateStep 1.to_date() greater than now.to_date() - 1.days
AND Send to BCStep 1 is true
AND StatusStep 1 does not equal Draft
AND Last Modified By IDStep 1 does not equal Workato_userProperties
AND StatusStep 1 does not equal In Approval Process

Re: Workato Trigger Behavior with Null Salesforce Date Fields

San — Thu, 20 Nov 2025 13:10:09 GMT

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

Re: Workato Trigger Behavior with Null Salesforce Date Fields

rajeshjanapati — Thu, 20 Nov 2025 16:44:47 GMT

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.

Re: Workato Trigger Behavior with Null Salesforce Date Fields

San — Fri, 21 Nov 2025 08:27:18 GMT

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

Re: Workato Trigger Behavior with Null Salesforce Date Fields

rajeshjanapati — Fri, 21 Nov 2025 08:35:03 GMT

Have you tried with Query?

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

Re: Workato Trigger Behavior with Null Salesforce Date Fields

shivakumara — Sat, 22 Nov 2025 07:14:40 GMT

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

Re: Workato Trigger Behavior with Null Salesforce Date Fields

San — Wed, 03 Dec 2025 11:57:30 GMT

@shivakumara - thank you for the detailed explanation. I was able to resolve the issue by adding a null check in my condition. Good to know that setting concurrency to more than 1 is also an another option.

Thank You

San