Subflow Error - "listenedTo" is not defined

[key_theshims]

Hello Community.

Can anyone advise on what to do with this Fault Description? 

Fault Description:  "listenedTo" is not defined

I have a subflow activity that needs to run inside a workflow and don't need any outputs since the next step is waiting for a condition.

[kaushal_snow]

Hi @key_theshims ,

Your error message "listenedTo is not defined" in a ServiceNow legacy workflow subflow typically indicates that the subflow is awaiting a signal or event that hasn't been properly configured or triggered. This situation often arises when the subflow is designed to listen for an event or signal that isn't being sent or received as expected.

Please review Subflow Configuration: Open the subflow check the "Wait for Signal" activity. Verify the signal name and ensure it matches the signal being sent.

Additionally, If your subflow and signal are in different scopes, ensure that the necessary permissions and access controls are configured to allow communication between them.

If you found my response helpful, please mark it as ‘Accept as Solution’ and ‘Helpful’. This helps other community members find the right answer more easily and supports the community.

[key_theshims]

Hi @kaushal_snow ,

my subflow has no required input (or 'Wait for Signal') and is set to trigger every time it's called from the workflow.

both the workflow and the subflow is in the same scoped application.

Is there any other place I can check?