Globus: UAB LTS, no individual allocation, hard to diagnose error

FYI Globus produces unhelpful errors if a researcher does not have any LTS allocations.

We saw this today with a researcher. I was assisting with getting LTS set up, not realizing their LTS individual allocation had not yet been set up. When they attempted to access the UAB LTS Mapped Collection "Credentials" page, the page spent some time loading (about 30 seconds) and then produced a yellow alert box with an error message.

The error contents appear to be related to a JS error.

{
"name": "TypeError",
"message": "Failed to fetch",
"stack": "TypeError: Failed to fetch\n at window.fetch (https://app.globus.org/assets/globus-c785a0d95fb96fc65e5ae3031f3c0005.js:5091:41)\n at n.Test.t.default (https://app.globus.org/assets/vendor-38b0546436276c2340d2e2a8ff7806f9.js:3192:126)\n at h (https://app.globus.org/assets/chunk.78.0f79d38e757ee41ad56f.js:11147:127)\n at h.next ()\n at https://app.globus.org/assets/chunk.78.0f79d38e757ee41ad56f.js:11153:105\n at new Promise ()\n at d (https://app.globus.org/assets/chunk.78.0f79d38e757ee41ad56f.js:11152:158)\n at i (https://app.globus.org/assets/chunk.78.0f79d38e757ee41ad56f.js:12898:144)\n at Object.get (https://app.globus.org/assets/chunk.78.0f79d38e757ee41ad56f.js:12899:49)\n at o.model (https://app.globus.org/assets/globus-c785a0d95fb96fc65e5ae3031f3c0005.js:3512:401)"
}

I will contact Globus support about improving the user experience for this case. In the meantime, if users encounter this kind of error configuring UAB LTS credentials for the first time, it's probably because they don't yet have an individual allocation. As a result, the UAB LTS Mapped Collection has no mapping "target", and Globus doesn't appear to have a graceful way of reporting that in the "Credentials" page.

No repository file or test is identified; start by reviewing issue 1130 and the reported Globus Credentials-page behavior. Check the outcome of the planned Globus support contact first. Done would require a defined repository change, such as confirmed user guidance or documentation of an upstream fix.