Getting "Invalid Update" when trying to update a Catalog Task in Workflow Editor on WashingtonDC.

[Jeff Welton1]

We are migrating from an old instance of ServiceNow to a new one.  Both are on WashintonDC.  I used the "Add to update set" utility to add the catalog item and workflow to the Update Set and then exported and imported the XML file. I did this first in my PDI with only 2 minor issues which I was able to address. However, after I migrated to our new DEV instance I am getting "Invalid update" when attempting to update the Fulfiller group on the Catalog Task activity in the workflow.  Even if I just open the task and save or update it without making any changes, I get the "Invalid Update:" error message.  If I insert a new task, it works fine.  I have dozens of Catalog items and Workflows that I will be migraing so I'd like to figure out what the issue is in my DEV instances since the migration works fine in my PDI.

Any ideas, thoughts, or pointers will be greatly appreciate.

Kind regards,

Jeff  

[Ravi Chandra_K]

Hello @Jeff Welton1 

Are there any fields (like reference) which has invalid value? This usually happens likely because one or more fields on the form view have an invalid value in it.

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0720622

Please mark the answer as helpful and correct if helped.

Kind regards,

Ravi Chandra 

[Jeff Welton1]

Hello @Ravi Chandra_K -

This was helpful, thank you.  However, it does not resolve my issue.  The one change I made was to add the "Notes" field to the Catalog Task activity form in the Workflow Editor.  I did the same thing in my PDI and did not have any issues. My PDI and the target instance are on WashingtonDC.  I checked other Catalog Task in other Workflows and did not have any issues.

Kind regards,

Jeff

[Jeff Welton1]

Hi @Ravi Chandra_K - 

I reached out to ServiceNow Support and they referred me to a knowledge base article addressing the error: Kindly refer to this link for more information on how to resolve the issue: https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0661926

[Ravi Chandra_K]

Hello @Jeff Welton1 

As mentioned in the support article, there might be custom schedule, custom time zone, or custom duration that does not exist on the target instance.

In that activity where you got an error, open that record. If you see sys id instead of schedule, timezone or duration, then you are missing those records in the Production. You have to take the xmls of those records, then you can commit.

Please mark the answer as helpful and correct if helped.

Kind regards,

Ravi Chandra