CircleCI: 404 for jobs for a seemingly-normal (yet old) pipeline

[jwodder]

While attemping to get a run of tinuous fetch against bids-specification on CircleCI using this configuration to complete successfully, I ran into a 404 error when attempting to list the workflow job details for pipeline 6927 (run at 2024-02-21T17:15:48Z). Strangely, although the pipeline came after (in reverse chronological order) a series of over a thousand pipelines that were skipped due to null workflow IDs (presumably because the records had expired?), this pipeline has a valid workflow ID, and a quick check reveals nothing unusual about it.

@yarikoptic How should this error be handled?

[yarikoptic]

if it sounds like a legit call, I think it might be wise long term to clear it up with circle ci support, e.g. I see similarish reports from the past https://discuss.circleci.com/t/workflow-links-result-in-404s-for-bitbucket-repos/13385 and they were addressed. Could you please search for possibly relevant and file if nothing yet?

If no quick feedback comes, then I guess we would be doomed to ignore those too :-/

[jwodder]

@yarikoptic I posted a question about this: https://discuss.circleci.com/t/expired-pipeline-not-represented-correctly-in-api/52934