Custom workflow is not getting triggerred in Yokohama pdi.

Rain Vaine
Kilo Sage

6 hours ago

Hello,

In the service now documentation, it mentions that if there is no condition set to a workflow, it will be triggered upon create of a record on that table.
In our upgraded client instance, the workflow works just fine.
In my Yokohama PDI, the workflow don't work.

Does anyone of you encountered a similar issue?

regards,
vaine

0 Helpfuls
  • 93 Views
1 REPLY 1

Naveen20
ServiceNow Employee

36m ago

Check these

1. Workflow is not Published/Active

On your PDI, open the workflow in the Workflow Editor and check if it's in a "Published" state. If it's still in "Draft" or "Checked Out" state, it won't fire. Click "Publish" to activate it.

2. Workflow Version Mismatch

Sometimes PDIs end up with multiple versions of the same workflow. Go to Workflow → Workflow Versions and filter by your workflow name. Make sure the latest version is the one that's published and that there aren't stale versions marked as active.

3. The Workflow Trigger Isn't Set Correctly

Even though the documentation says "no condition = triggers on insert," verify the trigger:

  • Open the workflow in the editor
  • Right-click the canvas → Workflow Properties
  • Confirm the Table is correct
  • Under the Conditions tab, ensure it says something like "Run on: Insert" (or "All" which includes insert)
  • If "Run on" is set to Update only, it won't fire on create

4. Missing Plugin or Dependency

Your client instance may have plugins activated that your PDI doesn't. Check if the workflow or the table it's attached to depends on a plugin that isn't active on your Yokohama PDI. Go to System Definition → Plugins and compare.

5. Scoped App Context

If the workflow belongs to a scoped application, make sure you're operating in the correct application scope on the PDI. The workflow won't trigger if the scope context is mismatched.

6. Event Queue / System Property Check

Verify these system properties on your PDI:

  • glide.workflow.enable should be true
  • Check System Diagnostics → Event Log to see if the workflow event is being generated at all when you create a record

try this below:

  1. Create a test record on the target table
  2. Go to Workflow → Contexts and filter by the table — do you see a context created?
  3. If no context exists, the trigger isn't firing at all, which points to the workflow not being published or the trigger configuration
  4. If a context exists but is stuck in "Executing" or "Error," open it to see where it failed
0 Helpfuls