From 1ddd86e312cfefc797d83913bd3d871d9f7f04ad Mon Sep 17 00:00:00 2001 From: JJRBEST Date: Wed, 24 Jun 2026 14:05:49 +0800 Subject: [PATCH 1/3] docs:Fixes #5257 --- docs/guides/max-execution-time.ipynb | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/guides/max-execution-time.ipynb b/docs/guides/max-execution-time.ipynb index ea6edf2133e..15005661ca5 100644 --- a/docs/guides/max-execution-time.ipynb +++ b/docs/guides/max-execution-time.ipynb @@ -42,7 +42,7 @@ "The maximum execution time for a job is the smaller of these values:\n", "\n", "- The value set for `max_execution_time`\n", - "- The service-determined job timeout value\n", + "- The service-enforced maximum limit (3 hours)\n", "\n", "The `max_execution_time` value is based on *QPU usage*, not wall clock time.\n", "\n", @@ -70,7 +70,7 @@ "\n", "## Service-calculated maximum execution time\n", "\n", - "The service calculates an appropriate job timeout value based on the input circuits and options. This service-calculated timeout is capped at 3 hours to ensure fair device usage. If a `max_execution_time` is also specified for the job, the lesser of the two values is used.\n", + "The service enforces a maximum execution time limit to ensure fair device usage. This limit is capped at 3 hours to ensure fair device usage. If a `max_execution_time` is also specified for the job, the lesser of the two values is used.\n", "\n", "For example, if you specify `max_execution_time=5000` (approximately 83 minutes), but the service determines it should not take more than 5 minutes (300 seconds) to execute the job, then the job is canceled after 5 minutes.\n", "\n", From 1616a44bfd4436fa0c18ed2c1415220a237d01d5 Mon Sep 17 00:00:00 2001 From: JJRBEST <128600131+JJRBEST@users.noreply.github.com> Date: Thu, 25 Jun 2026 09:24:40 +0800 Subject: [PATCH 2/3] Apply suggestions from code review Co-authored-by: Jessie Yu --- docs/guides/max-execution-time.ipynb | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/guides/max-execution-time.ipynb b/docs/guides/max-execution-time.ipynb index 15005661ca5..453a7e0aba2 100644 --- a/docs/guides/max-execution-time.ipynb +++ b/docs/guides/max-execution-time.ipynb @@ -29,7 +29,7 @@ "id": "a0d6acc5-754c-4955-8cf0-5e3e12b9dd1f", "metadata": {}, "source": [ - "To ensure fairness, there is a [service-calculated](#max-QPU) maximum amount of time each Qiskit Runtime job can run. If a job exceeds this time limit, it is forcibly canceled and a `RuntimeJobMaxTimeoutError` exception is raised. You can also [set a maximum execution time](#max-job) on your jobs to help control costs.\n", + "To ensure fairness, there is a [service-enforced](#max-QPU) maximum amount of time each Qiskit Runtime job can run. If a job exceeds this time limit, it is forcibly canceled and a `RuntimeJobMaxTimeoutError` exception is raised. You can also [set a maximum execution time](#max-job) on your jobs to help control costs.\n", "\n", "\n", " \n", @@ -68,9 +68,9 @@ "```\n", "\n", "\n", - "## Service-calculated maximum execution time\n", + "## Service-enforced maximum execution time\n", "\n", - "The service enforces a maximum execution time limit to ensure fair device usage. This limit is capped at 3 hours to ensure fair device usage. If a `max_execution_time` is also specified for the job, the lesser of the two values is used.\n", + "The service enforces a maximum execution time limit of 3 hours to ensure fair device usage. If a `max_execution_time` is also specified for the job, the lesser of the two values is used.\n", "\n", "For example, if you specify `max_execution_time=5000` (approximately 83 minutes), but the service determines it should not take more than 5 minutes (300 seconds) to execute the job, then the job is canceled after 5 minutes.\n", "\n", From 4903ffd9a608682f013aad504fdb6992d1d02658 Mon Sep 17 00:00:00 2001 From: JIAN JIA RUNG <128600131+JJRBEST@users.noreply.github.com> Date: Wed, 8 Jul 2026 09:29:36 +0800 Subject: [PATCH 3/3] Apply suggestions from code review Co-authored-by: Rebecca Dimock <66339736+beckykd@users.noreply.github.com> --- docs/guides/max-execution-time.ipynb | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/guides/max-execution-time.ipynb b/docs/guides/max-execution-time.ipynb index 453a7e0aba2..3d41756371c 100644 --- a/docs/guides/max-execution-time.ipynb +++ b/docs/guides/max-execution-time.ipynb @@ -42,7 +42,7 @@ "The maximum execution time for a job is the smaller of these values:\n", "\n", "- The value set for `max_execution_time`\n", - "- The service-enforced maximum limit (3 hours)\n", + "- The service-enforced maximum limit (three hours)\n", "\n", "The `max_execution_time` value is based on *QPU usage*, not wall clock time.\n", "\n", @@ -70,9 +70,9 @@ "\n", "## Service-enforced maximum execution time\n", "\n", - "The service enforces a maximum execution time limit of 3 hours to ensure fair device usage. If a `max_execution_time` is also specified for the job, the lesser of the two values is used.\n", + "The service enforces a maximum execution time limit of three hours to ensure fair device usage. If a `max_execution_time` is also specified for the job, the lesser of the two values is used.\n", "\n", - "For example, if you specify `max_execution_time=5000` (approximately 83 minutes), but the service determines it should not take more than 5 minutes (300 seconds) to execute the job, then the job is canceled after 5 minutes.\n", + "For example, if you specify `max_execution_time=5000` (approximately 83 minutes), then the job is canceled after approximately 83 minutes, even though the service could allow it to run for three hours.\n", "\n", "\n", "## Batch maximum execution time\n",