IBM webMethods Hybrid Integration

 View Only

 Pub/Sub document values null in triggered flow — webMethods 10.15

Ayushman Bokde's profile image
Ayushman Bokde posted 06/14/26 01:09 PM
Hi Everyone,
I am implementing a Publish/Subscribe pattern in webMethods 10.15 using pub.publish:publish
Setup:
Created a publishable document type
Created publish flow service
Created a trigger subscribing to it
Trigger fires correctly when I publish
 
Issue:
The triggered (subscriber) flow receives the document but all field values are null
I have referenced the same publishable document type in both the publish flow and the subscriber flow inputs
 
What I have verified:
Trigger is firing
Document type name is correct
Same publishable document used in both flows
 
Has anyone faced this issue? Any help is appreciated!
Kailash Kumar Mishra's profile image
Kailash Kumar Mishra posted 06/16/26 02:20 AM

Hi Ayushman.

Perhaps some things that you can try

  1. Validate that the Input of the Trigger Service has the Fully Qualified Name of the Document that is being published.
  2. If you have made any changes in the Document then try syncing the Document from the Designer to the Provider ( Broker or UM whatever applicable ).
  3. Look around if your Trigger Service or Publishing flow service has Pipeline debug set as Restore(Override) or Restore (Merge) and update it to None or Save.
  4. Clear IS Cache once and try publish again
Ayushman Bokde's profile image
Ayushman Bokde posted 06/16/26 11:34 AM

Thanks Kailash.

Resolved — Posting for anyone who faces the same issue:
Root Cause:
The issue was with the variable naming in both the publish and subscribe flows.
Solution:
Use the fully qualified namespace of the publishable document type as the variable name everywhere.
Example:
OrderProcessing.documents:orderConfirmedEvent
Apply this in:
  • Input variable name in the publish flow
  • Input variable name in the subscriber/triggered flow
  • documentTypeName field in pub.publish:publish
 
Once I used the full namespace consistently across all three places, the values started passing correctly to the subscriber flow.

Related Content