diff --git a/assets/workflows/progress/progress-cell-output-dark.png b/assets/workflows/progress/progress-cell-output-dark.png new file mode 100644 index 0000000..903f791 Binary files /dev/null and b/assets/workflows/progress/progress-cell-output-dark.png differ diff --git a/assets/workflows/progress/progress-cell-output-light.png b/assets/workflows/progress/progress-cell-output-light.png new file mode 100644 index 0000000..f7417a5 Binary files /dev/null and b/assets/workflows/progress/progress-cell-output-light.png differ diff --git a/workflows/progress.mdx b/workflows/progress.mdx index 65202f7..cfb0a60 100644 --- a/workflows/progress.mdx +++ b/workflows/progress.mdx @@ -136,6 +136,23 @@ Job( ) ``` +### Progress Display in interactive environments + +When running in an interactive environment such as a Jupyter notebook and the cell output is a Tilebox job object, the +job is automatically rendered, including its progress indicators. + + + ```python Python + job = job_client.find(job_id) + job # trigger notebook cell output + ``` + + + + Tilebox Workflows job object as Jupyter Cell output + Tilebox Workflows job object as Jupyter Cell output + + ## Progress idempotency Since tasks may fail and can subsequently be retried, it's possible that a task is executed more than once. This means that a task may report progress more than once.