Frequently asked Questions
If your question isn’t listed here, you may also find answers in the API and CLI FAQ.
All development happens on GitHub.
Check the Issues section to see whether your bug or idea has already been reported.
If not, feel free to open a new issue — we actively monitor the tracker and usually respond within a few days.
This error usually appears when the checksum calculation exceeds the default iBridges timeout of 25,000 seconds (~7 hours).
The transfer itself typically succeeds, but if the server is busy or the file is extremely large, the checksum step may run longer than the timeout.
You can increase the timeout by adding this entry to your irods_environment.json:
"connection_timeout": <time in seconds>
The maximum allowed value is:
"connection_timeout": 9208512000
which corresponds to roughly 292 years.
org_ don’t appear in iBridges
iBridges hides metadata keys beginning with org_ by default.
This behaviour is intentional on Yoda systems for data‑security reasons.
If you need to access these keys, you can do so via the
iBridges API.
Use the Search tab.
The search interface lets you filter for files regardless of their location.
Once the results appear, select the items you want to download.
Shared data in iRODS doesn’t always appear in your home or project collection.
However, shared objects must always reside in a collection you can access — that’s an iRODS rule.
To list all accessible collections:
- Open Search
- Set the search path to
/yourZone/home
- Use
Obj/Coll name: %
- Select Collections and unselect Data Objects
The results will show every collection you have permission to access.