In https://staging.hub.maap-project.org/ job output errors shows error from previously failed job

[chuckwondo]

Describe the bug

In https://staging.hub.maap-project.org/, when using the

To Reproduce

Steps to reproduce the behavior:

1. Go to https://staging.hub.maap-project.org/, and login, if not already logged in
2. Click on Environment and choose Other...
3. Enter the following for Custom image: mas.uat.maap-project.org/root/maap-workspaces/2i2c/pangeo:ogc-v1.0
4. Choose any value for Resource Allocation (or leave default value)
5. Press Start
6. Once instance is ready, from the Launcher, click the View My Jobs plugin

This assumes you have already run at least one job. In my case, my most recent job failed. When I start a new job and refresh the jobs list, when the new job is either "accepted" or "running", I select the job, then click the ERRORS tab below the job list, I see the error from the previously failed job.

Expected behavior

When selecting the currently accepted or running job, I expect the ERRORS tab to show nothing or wording such as "No output data available", not the error from the previously failed job.

Screenshots

Notice how the currently running job is selected, but that the ERRORS tab in the job details shows an error message. The error message is from the previously failed job, not the currently running job. I can confirm this by clicking on the previously failed job and see that the error message is identical, including the container ID mentioned in the error message (not visible in the screenshot).

[marjo-luc]

Resolved. Fix available in this image: mas.uat.maap-project.org/root/maap-workspaces/2i2c/pangeo:ogc-v1.0.1