Error in update set movement : Changes for table task failed to commit
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-18-2019 04:08 AM
Hi Friends,
We have created to custom tables, that are extend task table.
We have many fields into our custom tables and created new choice to state filed (task table field) where table is our task table.
But, we are facing some errors while we are moving update sets from Dev to another instance while committing update sets.
Can anyone please let me know, what can be reason for it, and can it be safe to move into PROD with these errors because we can commit update sets.
Errors:
1: Changes for table task failed to commit – this error we have faced in many update sets.
Also, this kind of message is coming while prevising and committing update sets.
Running child progress: Updating Schema - Adding Field(s)
Message from child progress: Adding "u_source_oth..." to task is 67% complete (118,000 of 176,000 rows)
Appreciate your response.
Thanks, Basant
- Labels:
-
Scripting and Coding
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-18-2019 04:21 AM
Hi Basant,
This may be because there are large number of records in task table. you can check with ServiceNow team on this.
Regards
Ankur
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-18-2019 04:44 AM
Hi Ankur,
thanks for your valuable reply.
are you referring your comment on this Changes for table task failed to commit or other question ?
as we checked and found, there 515728 records in task table.
thanks,
Basant SOni