I have a failing job that got triggered 12h ago that failed… and ever since then, for every single new build, the url redirects to that old job, such that I can no longer see the details of the correct job.
e.g. https://app.circleci.com/pipelines/github///433/workflows//jobs/386. That last number, 386 has not changed.
Good grief, even when falling back to the old UI, this same thing happens!! The job colour is green, but it redirects you to the older failed job!
I’m seeing something similar. Clicking through to jobs from a workflow ends up at jobs from earlier builds, not even the same job. It doesn’t happen reliably, and it doesn’t seem to be related to whether the job succeeded or failed, but once a link is wrong, it stays wrong. It will consistently link to the same, wrong, job.
Rebuilding a job with SSH seems to trigger this every time, but I’ve just had it happen with a workflow triggered directly from a GitHub change.
thanks, @andyduncanitv. That’s my experience as well. Specifically, if a job gets linked wrongly, it’ll stay that way. I haven’t had any issues with rerunning with SSH, though. If I see it, I’ll report back here.
This is likely related to an issue we had this week: https://status.circleci.com/incidents/qbzrj3vjm873
Due to the nature of the issue it was not possible for us to apply a universally safe correction to the corrupted data, please contact support if you need things corrected.
Yes, that does sound like what I was seeing. Thanks for the update.
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.