Reporting Issues
Include at least the following seven items in every report. Object IDs and reproduction steps are essential; without them, issues usually can't be pinpointed.
| # | Information | Example |
|---|---|---|
| 1 | Module | Data Workbench / Pipeline Processing |
| 2 | Time | 2026-10-20 15:42 (to the minute) |
| 3 | Object IDs | Curation project ID, data ID, pipeline job ID, dataset ID, training job ID, deployment ID |
| 4 | Steps to reproduce | 1. Open project X; 2. Click Pipeline; 3. Select SLAM; 4. Start processing |
| 5 | Expected result | Pipeline completes and outputs are ingested |
| 6 | Actual result | The SLAM operator failed at step 2 and the whole batch was marked failed |
| 7 | Logs | A screenshot of the page log or the copied log text |
Report Template
text
[Module]
[Time]
[Object IDs]
[Steps to reproduce]
1.
2.
3.
[Expected result]
[Actual result]
[Logs / screenshots]Don't include sensitive information
Never include passwords, tokens, access keys, or device keys in a report.

