Flow not triggering anymore, action's definition is missing

[Peter112]

I have a flow which seems to have stopped triggering at a specific day. I used to trigger on a case update and worked perfectly, until it didn't.
When I test the flow an manually enter a case ID which should have triggered the flow it works fine, but it won't trigger by itself.

When I open de flow and try to unpublish and publish it again it suddenly gives me an error on the OOTB 'Add comment to task' action.

But when I go to the action list it is there and active. And when I add the action step in the flow again it looks fine, until I try to publish the flow again. Then the error is back and the action step empty again.

When I lookup the sys_flow_record_trigger it looks fine, nothing seems to be missing.

We haven't changed anything at the moment the flow stopped working. The only thing I could find on that day is the Yokohama Patch 7 Hot Fix 2 update.
Does anybody have a clue what might be wrong?

[Ankur Bawiskar]

@Peter112 

sometimes simply removing and re-adding that action should fix this

Did you try that?

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[Peter112]

Hi @Ankur Bawiskar thank you for your response.

The action is the out of the box 'Add Comment To Task' action, it is read-only to me as an admin.

I haven't tried creating a copy. That might help although I feel that shouldn't be necessary for a default action.

[Ankur Bawiskar]

@Peter112 

you must have used this OOTB action in your flow or subflow

try removing that and add again and then publish your flow.

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[Peter112]

@Ankur Bawiskar that is correct, publishing the flow gives me the error twice because I used the action twice in the flow.
Removing and adding it doesn't help. I even tried to create a new test flow with only the action in it and it gave me the same errors when publishing.
I also tried this on our other instances but they give the same error.