Anyone receive an error message when trying to publish scoped application, "Progress worker state is not set to complete after worker is finished"?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-20-2020 06:52 AM
I am trying to publish my scoped application from my DEV instance into my TEST instance. However, I am receiving a failure error message when I click the submit button to publish.
Progress worker state is not set to complete after worker is finished
Any help is appreciated
- Labels:
-
Scoped App Development
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-20-2020 07:11 AM
This is supposed to be fixed, but does the behavior you're seeing match this HI article? If you're using the application repository now, maybe try publishing the application via an update set to see if it helps
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-16-2021 02:46 PM
The HI article you referenced gives me this error: "You do not have sufficient privileges to access this knowledge item".

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-27-2020 08:37 AM
Yes, I had this very issue, in fact still working with HI on finding a solution. I was able to make small progress.
The solution was to go into System Diagnostics/Progress Workers and filter to display any records where state = 'running'. Recommendation was to change the state from 'running' to 'complete' and then try and install the application again.
Note - This resolved the issue for one of my instances. I am still working with HI to figure out why I cannot publish the latest version in my STG instance. The issue in STG is now I have no records in 'running' state but I am still receiving the error.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-04-2021 08:34 AM
We had the same issue, it seems to be fixed in Paris per : PRB1342895 : The max length of sys_choice_set.element differs from sys_choice.element
the workaround provided is this:
The workaround is to set the sys_choice_set.element field max length to be the same as sys_choice.element (baseline is 80). The sys_update_xml generated from the update should be marked as replace on upgrade or removed unless you are trying to retain other customizations.
check to see if yours match.
yourinstance/sys_dictionary_list.do?sysparm_query=nameSTARTSWITHsys_choice%5Eelement%3Delement&sysparm_view=