Skip to main content

Hello all,

I'm encountering an automation issue that I thought adding a delay action would resolve—allowing sufficient time for all record data to populate before triggering the email.

 

The setup: Our work order base captures information and automatically emails the assigned technician. While most fields transfer correctly, two field agent fields consistently fail to appear: "Job Name" and "Scope of Work."

 

The first field:

 

The second field:

 

The workflow is: The PM manually enters the Scope of Work, which then populates both the Job Name and Job Summary fields. These should all be included in the technician's email.

The inconsistency: Manual testing of the automation shows all fields displaying correctly, but live submissions of new work orders result in missing Job Name and SOW data. I need the automation to run reliably without manual triggering, and populate those fields to the technician

 

 

Email output: 

 

Message body:

Any insights into what might be causing this? What am I doing wrong? 

Hmm, could I confirm that ‘Find Records’ step looking for the Job record that was just created, and that the Send Email step is using the result of the Find Record step?  If not, try that, should sort it out

When the record is first generated the Field Agent fields aren’t populated yet, and so the automation doesn’t have the data to work with.  By looking for the record after the delay, we grab the newly populated Field Agent data to use for the automation, does that make sense?

---

If that doesn’t work, you can try instead of using a Field Agent, what if you used an AI step in your automation instead?  And so it’d be:

  1. AI step to generate text
  2. Update record with that text
  3. Send email with that text
Terms & ConditionsAccessibility statement