Data Explorer

When working with Data Explorer, you might encounter the following issues.

Bucket visibility

A bucket you expect is missing from Data Explorer

You cannot see a bucket that you know exists.

On AWS, Data Explorer omits a bucket that the workspace credential cannot reach rather than showing it as inaccessible. This applies to every AWS credential type, including workload identity federation. A missing bucket and a bucket that does not exist look the same. Every member of the workspace sees the same bucket list for a given credential.

This is a cloud provider permission, not a Seqera Platform one. Changing your workspace role does not affect it. To resolve, ask your Platform administrator to grant the credential's role s3:ListBucket on that bucket. See Workload identity troubleshooting for the administrator-side steps.

Work directories

Work directory cannot be viewed in Data Explorer

The Data Explorer tab of the Task details dialog reports the following:

This work directory can't be viewed in Data Explorer.

The View button beside Work directory on the Run Info tab is disabled.

This issue occurs when the workspace has no visible data-link at the root of the bucket or container that holds the work directory. Seqera Platform matches a run's work directory against bucket-root data-links only. A data-link registered at a prefix such as s3://my-bucket/work never matches, and a hidden bucket-root data-link is excluded from the match.

To resolve, add a data-link at the bucket or container root, such as s3://my-bucket, and leave it visible. Your existing prefix-scoped data-links continue to work unchanged.

A visible bucket-root data-link lets every workspace member browse and download the whole bucket. See Isolate view, read, and write permissions to specific data repository paths.

If the work directory is not in cloud storage, such as a path on a high-performance computing (HPC) or local filesystem, Data Explorer cannot display it.