IdentityNow worfklow trigger filter not working proprerly

Identity Security Cloud (ISC) ISC Discussion and Questions
1

Hello!,

I’ve been testing the trigger filter from a worfklow that I’m making, the trigger is a “Identity Attributes Changed” type of filter.

The main problem is that regardless of what condition I set on the filter, the step of the filter is not working properly no matter the condition used in it. Let me attach some screenshots.

image
image1612×384 38.5 KB

As you can see in the pic above, the filter should avoid executing the workflow further than the first step (which is the trigger), but instead it keeps executing the workflow fully.

Regards!

2

image
image1890×927 145 KB

3

This filter should work. I tested something similar directly on a trigger subscription and it correctly filtered. I wonder if the filter wasn’t properly saved on the trigger subscription. Can you use the list trigger subscriptions API endpoint to check the filter that is applied on your workflow? You’ll get a list of trigger subscriptions, and you’ll need to find the correct subscription for your workflow. It should be named the same as your workflow. You should see a filter property that matches what you put in:

{
        "name": "Test Attribute Changed Filter",
        "id": "67d46539-f4bd-4130-ae6d-5e1670578bf8",
        "type": "WORKFLOW",
        "filter": "$.changes[?(@.attribute == \"email\")]",
        "enabled": true,
        "description": "Managed by Workflows",
        "triggerId": "idn:identity-attributes-changed",
        "responseDeadline": "PT1H",
        "workflowConfig": {
            "workflowId": "67d46539-f4bd-4130-ae6d-5e1670578bf8"
        },
        "triggerName": "Identity Attributes Changed"
    }
4

Hello, we’ve been trying to launch the worfklow correctly, and yes, it is enabled, and also the subscription is enabled also. But right now we’re getting none of our worfklows to be launched, and they gave no error. And in the activity log, does not appear the various unsuccessful runs launched. Maybe there’s happening this to other teams?, or maybe do you have any issues known related to the workflows not being launched at all?.

Regards.

5

@franciscojoserodrig1 If you haven’t already, please open a support ticket. Workflows not firing will need to be investigated by support to determine the root cause, which may require access to your tenant’s logs. This is something we can’t do in the developer community.

6

Okay Colin, thank you so much for your time.

Regards.

1 Like
7

I’m seeing the same problem on the same trigger

8

Hi @Mike_E, as Colin mentioned above, please open a support ticket. Workflows not firing will need to be investigated by support to determine the root cause, which may require access to your tenant’s logs. This is something we can’t do in the developer community.

You can open a support ticket here.

9

A post was split to a new topic: Workflow trigger filter invalid jsonpath