Yokohama - Orchestration Databus Output is Empty

Wendy Peterson
Giga Guru

I have hundreds of workflows where we use AD Activities to Add and Remove. I use these scratchpads after successful or failed. They are no longer bringing back any data even though I see it's being written to the ECC Queue correctly

 

Here are some screenshots on what happens today it returns DATA whether it be successful, skipped or error. After Yokohama top screenshot. Bottom screenshot is today

 

2025-07-30_06-20-17.jpg2025-07-30_06-15-52.jpg

 
Example of error in ECC Queue
<error>(&amp;(objectClass=Group)(samaccountname=GG_TFS_Restricted_DBATeam_Contributorr)) could not be found
HRESULT: [-2147024809]

Example of Normal Output when Successful

<output>
SKIPPED: 40635 Already a member of 'GG_TFS_Restricted_DBATeam_Contributor'

or
<output>
SUCCESS: 40635 Added to 'GG_TFS_Restricted_DBATeam_Contributor'
 

 

 

workflow.scratchpad.output = data.get(19).output;
current.work_notes = 'AD Provisioning Information: ' + workflow.scratchpad.output;

or failed

workflow.scratchpad.error = data.get(19).errorMessage;
current.work_notes = 'AD Provisioning Information: ' + workflow.scratchpad.error;
current.u_orchestration_failed = 'true';

 

4 REPLIES 4

It's Orchestration in the workflow that worked till Yokohama so my guess is they changed something. It doesn't even show the 'successful' activity correct anymore

 

Hi @Wendy Peterson 

Check this documentation for deprecated activities -List of Orchestration activities

Could you also check if the workflow is showing similar behavior for 'Remove User" activity ?