Jobs Dashboard displays Something Went Wrong

If you are unable to view the jobs dashboard of your project in Domino 4.x, you may have run into a known issue with the timeline feature of the jobs dashboard.  The 'Something Went Wrong' failure can have several root causes, many of which are just transient and a screen refresh will resolve the issue for you. 

In this case the error is persistent and you cannot regain access to the jobs dashboard without first minimizing the jobs timeline.  

This problem is usually caused by the sort query exceeding the set limit of 1Gb.
There are a few methods to confirm this problem. Exploring the actual request via the browser developer console you will be able to see a 500 response to a GET request to URL:

https://www.<YOUR_DEPLOYMENT_URL>.com/v4/jobs/timeline/project/<HASH>

The second symptom can be observed in the frontend logs and would appear similar to: 

<TIME_DATE> Caused by: com.mongodb.MongoCommandException: \
Command failed with error 16820 (Location16820): \
‘Sort exceeded memory limit of 104857600 bytes, \
but did not opt in to external sorting.’ on server \
<MONGO_SERVER_REPLICA_NUMBER>:27017. The full response is \
{“operationTime”: {“$timestamp”: {“t”: <TIMESTAMP> , “i”: 8}}, “ok”: 0.0, \
“errmsg”: “Sort exceeded memory limit of 104857600 bytes, but did not opt \
in to external sorting.“..........

This issue will be fixed in Domino 5.1.

In the meantime to correct this issue and unblock your jobs dashboard there are 2 workarounds

First method is to try the following.  

1) Record the Browser URI for the project where you see the failure, e.g.

https://<your-deployment>/jobs/<userid>/<project-name>

Open your browser to any other project you own and navigate to the jobs dashboard.  Notice at the top of the dashboard you will see timeline displayed...

2) Minimize the jobs timeline using the ^ symbol next to 'Jobs Timeline'

You should now see the timeline go away...

3) Now in the same tab, rewrite the URI to point to your original project with the failing jobs dashboard

Your Jobs dashboard should now be visible without the timeline visible.

If the previous solution does not work for you then you can try the second method which os to 
copy the project.  Since a copy of the project does not bring the jobs execution history this issue 
will no longer be a problem in the copied version.  Fork would also work however it will create a
dependancy with the original project. 

Since this problem occurs due to the size of the query that is occurring to populate the jobs timeline.  The problem can occur with as few as 50 completed jobs in the project.  But it can vary greatly depending on how many objects (datasets, imports, git repositories) are attached to the project.  And you may not see this error occur until you have thousands of jobs in the project.