Knowledge article from HR Knowledge Base is being set to retired without clicking Retire UI Action

Vdevmat33
Tera Contributor

‎02-10-2025 05:13 AM

Hi Team,

 

There is a weird scenario which i came across recently.

 

Knowledge Articles from HR Knowledge Base are instantly getting retired without clicking on Retire UI Action when any change is made on knowledge article when it's in published state.

 

Scenario 1: When i tried to extend the validity of a knowledge article using custom UI Action, the validity got extended but the workflow state was

set to retired without triggering any approval.

 

Scenario 2: When i tried to update the knowledge article author from list view using list context menu, the author got updated but workflow state was set to retired without triggering any approval.

 

What could be the possible reasons for such behaviour. Could someone please suggest.

 

Thanks!

0 Helpfuls
  • 357 Views
1 REPLY 1

Rob Sestito
Mega Sage

‎02-10-2025 08:01 AM

Hello @Vdevmat33 - 

 

Do you happen to have Versioning on for your articles? I have not used versioning in a while (never really liked it), but I am wondering if possible that with these little changes you are making to the articles, that it is pushing out a whole new version of the article and setting the older one to retired. Have you been able to check your list of articles if there are duplicates (duplicate titles) and the version is different? I would throw the Version column in your list view to help check. It almost sounds like this is happening.

 

But if you are not using versioning and/ or have already checked on this. Then maybe there is something wrong with the flow being used on your articles/bases that is for some reason being triggered and setting your article to retired when making any kind of change.

 

Might be worth looking at.

-Rob

0 Helpfuls