Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

After clone, SOW not showing up

nebiata
Tera Expert

Hello,

I was working on sow on your dev instance, before cloning the dev instance, I backed my update sets and put it back in dev after the clone. I also installed the plugins. Now when I click service operations workspace, I get a screen saying The page you are looking for could not be found. 

nebiata_0-1706190819331.png

I need help and urgent.

 

Thank you

1 ACCEPTED SOLUTION

Shaqeel
Mega Sage
Mega Sage

Hi @nebiata 

 

If your SOW is not showing up after a clone in ServiceNow, it could be due to several reasons. Here are some troubleshooting steps:

1. Check the Clone Logs:
- Go to System Diagnostics > Stats > Stats Logs.
- Look for any errors or warnings related to the cloning process.

2. Verify the Data Preserved During Cloning:
- ServiceNow allows you to preserve certain data during the cloning process.
- Go to System Clone > Exclude Data and check if the SOW or related tables were excluded.

3. Check the Access Control Lists (ACLs):
- Ensure that the user has the necessary permissions to view the SOW.
- Go to System Security > Access Control and check the ACLs for the SOW table.

4. Verify the SOW Record:
- Check if the SOW record exists in the cloned instance.
- If it exists, ensure that it is not being filtered out due to any conditions or business rules.

5. Check for Custom Scripts:
- If there are any custom scripts running on the SOW table, they might be causing the issue.
- Check the scripts for any errors or conflicts.

6. Contact ServiceNow Support:
- If you are unable to resolve the issue, contact ServiceNow support for further assistance.

 

Regards

Shaqeel


***********************************************************************************************************************
If my response proves useful, please indicate its helpfulness by selecting "Accept as Solution" and " Helpful." This action benefits both the community and me.

***********************************************************************************************************************





Regards

Shaqeel

View solution in original post

1 REPLY 1

Shaqeel
Mega Sage
Mega Sage

Hi @nebiata 

 

If your SOW is not showing up after a clone in ServiceNow, it could be due to several reasons. Here are some troubleshooting steps:

1. Check the Clone Logs:
- Go to System Diagnostics > Stats > Stats Logs.
- Look for any errors or warnings related to the cloning process.

2. Verify the Data Preserved During Cloning:
- ServiceNow allows you to preserve certain data during the cloning process.
- Go to System Clone > Exclude Data and check if the SOW or related tables were excluded.

3. Check the Access Control Lists (ACLs):
- Ensure that the user has the necessary permissions to view the SOW.
- Go to System Security > Access Control and check the ACLs for the SOW table.

4. Verify the SOW Record:
- Check if the SOW record exists in the cloned instance.
- If it exists, ensure that it is not being filtered out due to any conditions or business rules.

5. Check for Custom Scripts:
- If there are any custom scripts running on the SOW table, they might be causing the issue.
- Check the scripts for any errors or conflicts.

6. Contact ServiceNow Support:
- If you are unable to resolve the issue, contact ServiceNow support for further assistance.

 

Regards

Shaqeel


***********************************************************************************************************************
If my response proves useful, please indicate its helpfulness by selecting "Accept as Solution" and " Helpful." This action benefits both the community and me.

***********************************************************************************************************************





Regards

Shaqeel