id stringlengths 21 21 | kind stringclasses 3
values | options listlengths 2 6 | target listlengths 2 6 | state stringlengths 150 227 | question stringclasses 7
values | domain stringclasses 1
value | family stringclasses 1
value | source stringclasses 1
value |
|---|---|---|---|---|---|---|---|---|
v3_b18631e5000a4323_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.01,
0,
0,
0.02,
0.51,
0.46
] | A model retrain needs 4 hours but the window is 90 minutes; additionally has a hard customer-facing deadline. Context: on the first of the month, while legacy systems are still active. Reported by the automated check. | Rate deadline feasibility for this scenario on a 0-5 scale. | scheduling | agent | yuri_v3 |
v3_c1d7b454e664c2cc_n | noul | [
"false",
"true"
] | [
0.75,
0.25
] | The batch job requires exclusive database access; additionally can run on any replica. Context: this Friday, during the system migration. Reported by the on-call engineer. | Is this scenario one where: retries are safe here? | scheduling | agent | yuri_v3 |
v3_8190236b832a207b_n | noul | [
"false",
"true"
] | [
0.3,
0.7
] | The batch job fits entirely inside the quiet period; additionally can run on any replica. Context: this Friday, during the system migration. Reported by the on-call engineer. | Is this scenario one where: this window is safe? | scheduling | agent | yuri_v3 |
v3_f35b2b198214df64_n | noul | [
"false",
"true"
] | [
0.2,
0.8
] | A model retrain is idempotent and safe to retry; additionally needs 4 hours but the window is 90 minutes. Context: on the first of the month, during the morning shift. Reported by the review queue. | Is this scenario one where: retries are safe here? | scheduling | agent | yuri_v3 |
v3_7fc8ba8fc710cd08_n | noul | [
"false",
"true"
] | [
0.94,
0.06
] | The report generation has run over its window 3 weeks straight; additionally requires exclusive database access. Context: this Friday, immediately after go-live. Reported by the supervisor. | Is this scenario one where: this window is safe? | scheduling | agent | yuri_v3 |
v3_f7b137331fc47694_n | noul | [
"false",
"true"
] | [
0.12,
0.88
] | A maintenance window needs 4 hours but the window is 90 minutes; additionally collides with the nightly backup. Context: on the first of the month, following a recent audit. Reported by the on-call engineer. | Is this scenario one where: the job will miss its deadline? | scheduling | agent | yuri_v3 |
v3_3d6c051a65bac131_n | noul | [
"false",
"true"
] | [
0.74,
0.26
] | The report generation fits entirely inside the quiet period; additionally shares a lock with the payroll run. Context: every 4 hours, during the quarterly review. Reported by the on-call engineer. | Is this scenario one where: retries are safe here? | scheduling | agent | yuri_v3 |
v3_5176d74a3966dec4_n | noul | [
"false",
"true"
] | [
0.64,
0.36
] | A model retrain requires exclusive database access; additionally can run on any replica. Context: every 4 hours, with staffing at reduced levels. Reported by the supervisor. | Is this scenario one where: this window is safe? | scheduling | agent | yuri_v3 |
v3_726271be9ea26269_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0.03,
0.6,
0.37,
0
] | The report generation collides with the nightly backup; additionally depends on a task that runs at 03:00. Context: every 4 hours, during a scheduled maintenance window. Reported by the monitoring system. | Rate deadline feasibility for this scenario on a 0-5 scale. | scheduling | agent | yuri_v3 |
v3_80c3866264e50ac4_c | choice | [
"critical",
"high",
"normal",
"low"
] | [
0.97,
0.03,
0,
0
] | The batch job has a hard customer-facing deadline; additionally depends on a task that runs at 03:00. Context: on the first of the month, mid-incident. Reported by the supervisor. | Priority for this scenario. | scheduling | agent | yuri_v3 |
v3_7b31890ea9a81dfe_c | choice | [
"critical",
"high",
"normal",
"low"
] | [
0.38,
0.55,
0.02,
0.05
] | The report generation requires exclusive database access; additionally depends on a task that runs at 03:00. Context: during peak traffic, during the system migration. Reported by the review queue. | Priority for this scenario. | scheduling | agent | yuri_v3 |
v3_5616779ad606877a_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.0101,
0.0101,
0.0808,
0.2727,
0.5556,
0.0707
] | A model retrain has run over its window 3 weeks straight; additionally can run on any replica. Context: every 4 hours, during the quarterly review. Reported by the review queue. | Rate deadline feasibility for this scenario on a 0-5 scale. | scheduling | agent | yuri_v3 |
v3_cd0cb9048980d434_c | choice | [
"run_now",
"delay",
"split_window",
"move_to_next_slot"
] | [
0.81,
0.1,
0.01,
0.08
] | The report generation has a hard customer-facing deadline; additionally fits entirely inside the quiet period. Context: on the first of the month, under an active deadline. Reported by the on-call engineer. | Schedule action for this scenario. | scheduling | agent | yuri_v3 |
v3_964681dfb965d324_n | noul | [
"false",
"true"
] | [
0.07,
0.93
] | The report generation depends on a task that runs at 03:00; additionally needs 4 hours but the window is 90 minutes. Context: every 4 hours, as part of a compliance sweep. Reported by the automated check. | Is this scenario one where: the job will miss its deadline? | scheduling | agent | yuri_v3 |
v3_fe96edc842949e57_c | choice | [
"run_now",
"delay",
"split_window",
"move_to_next_slot"
] | [
0.04,
0.33,
0.17,
0.46
] | The report generation collides with the nightly backup; additionally has a hard customer-facing deadline. Context: during peak traffic, mid-incident. Reported by the review queue. | Schedule action for this scenario. | scheduling | agent | yuri_v3 |
v3_e405d96539bfa4de_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.14,
0.82,
0.04
] | The batch job has a hard customer-facing deadline; additionally shares a lock with the payroll run. Context: on the first of the month, with staffing at reduced levels. Reported by the review queue. | Rate deadline feasibility for this scenario on a 0-5 scale. | scheduling | agent | yuri_v3 |
v3_7b31890ea9a81dfe_n | noul | [
"false",
"true"
] | [
0.28,
0.72
] | The report generation requires exclusive database access; additionally depends on a task that runs at 03:00. Context: during peak traffic, during the system migration. Reported by the review queue. | Is this scenario one where: the job will miss its deadline? | scheduling | agent | yuri_v3 |
v3_6adc78064708f396_c | choice | [
"critical",
"high",
"normal",
"low"
] | [
0.07,
0.5,
0.28,
0.15
] | A maintenance window can run on any replica; additionally is idempotent and safe to retry. Context: every 4 hours, under an active deadline. Reported by the on-call engineer. | Priority for this scenario. | scheduling | agent | yuri_v3 |
v3_bbf8f8aab4ba1ddb_n | noul | [
"false",
"true"
] | [
0.15,
0.85
] | A maintenance window is idempotent and safe to retry; additionally requires exclusive database access. Context: this Friday, during normal operations. Reported by the monitoring system. | Is this scenario one where: retries are safe here? | scheduling | agent | yuri_v3 |
v3_7cd9c7019fc457c7_n | noul | [
"false",
"true"
] | [
0.54,
0.46
] | A maintenance window has a hard customer-facing deadline; additionally requires exclusive database access. Context: this Friday, during an external partner integration. Reported by the review queue. | Is this scenario one where: the job will miss its deadline? | scheduling | agent | yuri_v3 |
v3_2c72f543131a318b_n | noul | [
"false",
"true"
] | [
0.73,
0.27
] | The batch job depends on a task that runs at 03:00; additionally has a hard customer-facing deadline. Context: on the first of the month, during the holiday freeze. Reported by the supervisor. | Is this scenario one where: retries are safe here? | scheduling | agent | yuri_v3 |
v3_11440afdef376670_c | choice | [
"critical",
"high",
"normal",
"low"
] | [
0.29,
0.7,
0.01,
0
] | A maintenance window can run on any replica; additionally has a hard customer-facing deadline. Context: every 4 hours, under an active deadline. Reported by the supervisor. | Priority for this scenario. | scheduling | agent | yuri_v3 |
v3_e40c6776e9b347ec_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0.01,
0.39,
0.59,
0.01
] | A maintenance window collides with the nightly backup; additionally shares a lock with the payroll run. Context: this Friday, during normal operations. Reported by the monitoring system. | Rate deadline feasibility for this scenario on a 0-5 scale. | scheduling | agent | yuri_v3 |
v3_1e843a7835613ce1_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.01,
0.6,
0.39
] | The report generation shares a lock with the payroll run; additionally needs 4 hours but the window is 90 minutes. Context: during peak traffic, under reduced staffing. Reported by the monitoring system. | Rate schedule conflict risk for this scenario on a 0-5 scale. | scheduling | agent | yuri_v3 |
v3_38f92dbbbef370c2_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.0101,
0.0404,
0.2626,
0.5657,
0.1212,
0
] | A maintenance window collides with the nightly backup; additionally is idempotent and safe to retry. Context: on the first of the month, during normal operations. Reported by the on-call engineer. | Rate deadline feasibility for this scenario on a 0-5 scale. | scheduling | agent | yuri_v3 |
v3_7a1b3bcabf603b44_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.05,
0.85,
0.1
] | The report generation has a hard customer-facing deadline; additionally collides with the nightly backup. Context: this Friday, while legacy systems are still active. Reported by the automated check. | Rate schedule conflict risk for this scenario on a 0-5 scale. | scheduling | agent | yuri_v3 |
v3_b84d6efb2a130ec6_n | noul | [
"false",
"true"
] | [
0.21,
0.79
] | A maintenance window has a hard customer-facing deadline; additionally has run over its window 3 weeks straight. Context: this Friday, immediately after go-live. Reported by the review queue. | Is this scenario one where: the job will miss its deadline? | scheduling | agent | yuri_v3 |
v3_8a358762d040275d_c | choice | [
"run_now",
"delay",
"split_window",
"move_to_next_slot"
] | [
0.14,
0.18,
0.06,
0.62
] | A maintenance window is idempotent and safe to retry; additionally has run over its window 3 weeks straight. Context: during peak traffic, during an external partner integration. Reported by the automated check. | Schedule action for this scenario. | scheduling | agent | yuri_v3 |
v3_b4e6105adf33b301_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.03,
0.03,
0.13,
0.29,
0.47,
0.05
] | A maintenance window fits entirely inside the quiet period; additionally has run over its window 3 weeks straight. Context: on the first of the month, during normal operations. Reported by the review queue. | Rate deadline feasibility for this scenario on a 0-5 scale. | scheduling | agent | yuri_v3 |
v3_5e86c0ae63d198c5_c | choice | [
"run_now",
"delay",
"split_window",
"move_to_next_slot"
] | [
0.59,
0.19,
0.03,
0.19
] | A model retrain can run on any replica; additionally fits entirely inside the quiet period. Context: on the first of the month, while legacy systems are still active. Reported by the supervisor. | Schedule action for this scenario. | scheduling | agent | yuri_v3 |
v3_dd5802051892c739_n | noul | [
"false",
"true"
] | [
0.13,
0.87
] | A maintenance window is idempotent and safe to retry; additionally depends on a task that runs at 03:00. Context: during peak traffic, as part of a compliance sweep. Reported by the monitoring system. | Is this scenario one where: retries are safe here? | scheduling | agent | yuri_v3 |
v3_2ce36788c5a4a8e5_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0.01,
0.13,
0.79,
0.07
] | The batch job has a hard customer-facing deadline; additionally collides with the nightly backup. Context: every 4 hours, at the end of the fiscal period. Reported by the review queue. | Rate deadline feasibility for this scenario on a 0-5 scale. | scheduling | agent | yuri_v3 |
v3_a4addaa74443e2fb_n | noul | [
"false",
"true"
] | [
0.8,
0.2
] | A maintenance window collides with the nightly backup; additionally has a hard customer-facing deadline. Context: during peak traffic, while legacy systems are still active. Reported by the operator. | Is this scenario one where: retries are safe here? | scheduling | agent | yuri_v3 |
v3_978f38945761e527_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.27,
0.72,
0.01
] | A maintenance window shares a lock with the payroll run; additionally depends on a task that runs at 03:00. Context: this Friday, following a recent audit. Reported by the review queue. | Rate schedule conflict risk for this scenario on a 0-5 scale. | scheduling | agent | yuri_v3 |
v3_3922aeb499097236_c | choice | [
"critical",
"high",
"normal",
"low"
] | [
0.29,
0.68,
0.01,
0.02
] | The batch job needs 4 hours but the window is 90 minutes; additionally fits entirely inside the quiet period. Context: on the first of the month, with staffing at reduced levels. Reported by the supervisor. | Priority for this scenario. | scheduling | agent | yuri_v3 |
v3_c8bddfce9d6df726_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.07,
0.26,
0.21,
0.35,
0.1,
0.01
] | The report generation depends on a task that runs at 03:00; additionally fits entirely inside the quiet period. Context: during peak traffic, during an external partner integration. Reported by the review queue. | Rate schedule conflict risk for this scenario on a 0-5 scale. | scheduling | agent | yuri_v3 |
v3_b1ca816debe78bd2_n | noul | [
"false",
"true"
] | [
0.87,
0.13
] | A model retrain has run over its window 3 weeks straight; additionally shares a lock with the payroll run. Context: this Friday, during the system migration. Reported by the monitoring system. | Is this scenario one where: retries are safe here? | scheduling | agent | yuri_v3 |
v3_01d65f19a5cc6510_c | choice | [
"run_now",
"delay",
"split_window",
"move_to_next_slot"
] | [
0.01,
0.28,
0.06,
0.65
] | A model retrain has a hard customer-facing deadline; additionally needs 4 hours but the window is 90 minutes. Context: during peak traffic, at the end of the fiscal period. Reported by the operator. | Schedule action for this scenario. | scheduling | agent | yuri_v3 |
v3_0c23f199bd2a40fa_c | choice | [
"run_now",
"delay",
"split_window",
"move_to_next_slot"
] | [
0.12,
0.41,
0.03,
0.44
] | A maintenance window has run over its window 3 weeks straight; additionally is idempotent and safe to retry. Context: during peak traffic, mid-incident. Reported by the operator. | Schedule action for this scenario. | scheduling | agent | yuri_v3 |
v3_406aaeefe3934514_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.1,
0.83,
0.07
] | The batch job has a hard customer-facing deadline; additionally depends on a task that runs at 03:00. Context: this Friday, during peak load. Reported by the automated check. | Rate schedule conflict risk for this scenario on a 0-5 scale. | scheduling | agent | yuri_v3 |
v3_456ece499d70961e_n | noul | [
"false",
"true"
] | [
0.72,
0.28
] | The batch job fits entirely inside the quiet period; additionally has a hard customer-facing deadline. Context: this Friday, following a recent audit. Reported by the review queue. | Is this scenario one where: the job will miss its deadline? | scheduling | agent | yuri_v3 |
v3_42b45a84881b1cb7_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.01,
0.54,
0.45
] | The report generation needs 4 hours but the window is 90 minutes; additionally depends on a task that runs at 03:00. Context: during peak traffic, at the end of the fiscal period. Reported by the on-call engineer. | Rate schedule conflict risk for this scenario on a 0-5 scale. | scheduling | agent | yuri_v3 |
v3_678e10027bb8b984_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0.01,
0.16,
0.75,
0.08
] | A model retrain shares a lock with the payroll run; additionally requires exclusive database access. Context: every 4 hours, during the quarterly review. Reported by the automated check. | Rate schedule conflict risk for this scenario on a 0-5 scale. | scheduling | agent | yuri_v3 |
v3_5bc05450c51f1cf8_c | choice | [
"critical",
"high",
"normal",
"low"
] | [
0.05,
0.56,
0.34,
0.05
] | The batch job requires exclusive database access; additionally is idempotent and safe to retry. Context: every 4 hours, during an external partner integration. Reported by the supervisor. | Priority for this scenario. | scheduling | agent | yuri_v3 |
v3_9439268a695c0aaf_c | choice | [
"critical",
"high",
"normal",
"low"
] | [
0.02,
0.52,
0.34,
0.12
] | A maintenance window can run on any replica; additionally depends on a task that runs at 03:00. Context: this Friday, under reduced staffing. Reported by the automated check. | Priority for this scenario. | scheduling | agent | yuri_v3 |
v3_8668a5d247a8065a_c | choice | [
"run_now",
"delay",
"split_window",
"move_to_next_slot"
] | [
0.32,
0.05,
0.46,
0.17
] | The report generation has a hard customer-facing deadline; additionally shares a lock with the payroll run. Context: this Friday, under reduced staffing. Reported by the operator. | Schedule action for this scenario. | scheduling | agent | yuri_v3 |
v3_479c0762dfe167b6_n | noul | [
"false",
"true"
] | [
0.66,
0.34
] | A model retrain needs 4 hours but the window is 90 minutes; additionally can run on any replica. Context: this Friday, during the system migration. Reported by the supervisor. | Is this scenario one where: retries are safe here? | scheduling | agent | yuri_v3 |
v3_c5676653e135443a_n | noul | [
"false",
"true"
] | [
0.7,
0.3
] | The report generation collides with the nightly backup; additionally depends on a task that runs at 03:00. Context: every 4 hours, as part of a compliance sweep. Reported by the automated check. | Is this scenario one where: retries are safe here? | scheduling | agent | yuri_v3 |
v3_07b854a92e33c08b_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.04,
0.71,
0.25
] | A model retrain has a hard customer-facing deadline; additionally has run over its window 3 weeks straight. Context: this Friday, at the end of the fiscal period. Reported by the operator. | Rate deadline feasibility for this scenario on a 0-5 scale. | scheduling | agent | yuri_v3 |
v3_1b6726e6fc562701_n | noul | [
"false",
"true"
] | [
0.44,
0.56
] | The batch job is idempotent and safe to retry; additionally has a hard customer-facing deadline. Context: during peak traffic, during a scheduled maintenance window. Reported by the supervisor. | Is this scenario one where: this window is safe? | scheduling | agent | yuri_v3 |
v3_5ba81be97570a754_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.07,
0.06,
0.13,
0.5,
0.22,
0.02
] | A maintenance window requires exclusive database access; additionally is idempotent and safe to retry. Context: during peak traffic, under reduced staffing. Reported by the supervisor. | Rate deadline feasibility for this scenario on a 0-5 scale. | scheduling | agent | yuri_v3 |
v3_ffedbdd2de4cc6b6_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.0404,
0.2222,
0.5657,
0.1717,
0
] | A maintenance window shares a lock with the payroll run; additionally is idempotent and safe to retry. Context: every 4 hours, during a scheduled maintenance window. Reported by the review queue. | Rate schedule conflict risk for this scenario on a 0-5 scale. | scheduling | agent | yuri_v3 |
v3_9751eb1f4f6cee23_c | choice | [
"critical",
"high",
"normal",
"low"
] | [
0.11,
0.58,
0.08,
0.23
] | A model retrain can run on any replica; additionally collides with the nightly backup. Context: this Friday, during the holiday freeze. Reported by the supervisor. | Priority for this scenario. | scheduling | agent | yuri_v3 |
v3_6279b885245312c4_c | choice | [
"critical",
"high",
"normal",
"low"
] | [
0.06,
0.71,
0.16,
0.07
] | The batch job can run on any replica; additionally shares a lock with the payroll run. Context: on the first of the month, with staffing at reduced levels. Reported by the automated check. | Priority for this scenario. | scheduling | agent | yuri_v3 |
v3_e90bfb7566899278_c | choice | [
"critical",
"high",
"normal",
"low"
] | [
0.68,
0.32,
0,
0
] | A maintenance window has a hard customer-facing deadline; additionally depends on a task that runs at 03:00. Context: during peak traffic, at the end of the fiscal period. Reported by the on-call engineer. | Priority for this scenario. | scheduling | agent | yuri_v3 |
v3_bce29b58c6fe1a94_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0.01,
0.21,
0.75,
0.03
] | A model retrain requires exclusive database access; additionally shares a lock with the payroll run. Context: every 4 hours, as part of a compliance sweep. Reported by the supervisor. | Rate schedule conflict risk for this scenario on a 0-5 scale. | scheduling | agent | yuri_v3 |
v3_e19ff2fec36ae171_n | noul | [
"false",
"true"
] | [
0.79,
0.21
] | The report generation shares a lock with the payroll run; additionally has a hard customer-facing deadline. Context: this Friday, during normal operations. Reported by the automated check. | Is this scenario one where: retries are safe here? | scheduling | agent | yuri_v3 |
v3_7baf9898afad0cc4_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.24,
0.53,
0.16,
0.07,
0,
0
] | The batch job is idempotent and safe to retry; additionally can run on any replica. Context: on the first of the month, as part of a compliance sweep. Reported by the on-call engineer. | Rate schedule conflict risk for this scenario on a 0-5 scale. | scheduling | agent | yuri_v3 |
v3_86596c46aa7b47da_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.1313,
0.8182,
0.0505
] | A model retrain depends on a task that runs at 03:00; additionally has run over its window 3 weeks straight. Context: every 4 hours, while legacy systems are still active. Reported by the on-call engineer. | Rate schedule conflict risk for this scenario on a 0-5 scale. | scheduling | agent | yuri_v3 |
v3_660025a22a961ac7_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.02,
0.06,
0.16,
0.6,
0.15,
0.01
] | A maintenance window can run on any replica; additionally requires exclusive database access. Context: on the first of the month, with staffing at reduced levels. Reported by the monitoring system. | Rate deadline feasibility for this scenario on a 0-5 scale. | scheduling | agent | yuri_v3 |
v3_cc712fe4a8d0f7f3_n | noul | [
"false",
"true"
] | [
0.64,
0.36
] | The report generation can run on any replica; additionally needs 4 hours but the window is 90 minutes. Context: every 4 hours, under reduced staffing. Reported by the monitoring system. | Is this scenario one where: retries are safe here? | scheduling | agent | yuri_v3 |
v3_2ff71db43a5fa02a_n | noul | [
"false",
"true"
] | [
0.85,
0.15
] | A model retrain collides with the nightly backup; additionally can run on any replica. Context: every 4 hours, as part of a compliance sweep. Reported by the operator. | Is this scenario one where: this window is safe? | scheduling | agent | yuri_v3 |
v3_e95f6ba8fd6e1ad8_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.01,
0,
0.01,
0.03,
0.53,
0.42
] | The batch job requires exclusive database access; additionally needs 4 hours but the window is 90 minutes. Context: during peak traffic, following a recent audit. Reported by the monitoring system. | Rate deadline feasibility for this scenario on a 0-5 scale. | scheduling | agent | yuri_v3 |
v3_481aea41c42466c6_c | choice | [
"run_now",
"delay",
"split_window",
"move_to_next_slot"
] | [
0.01,
0.06,
0.35,
0.58
] | The report generation depends on a task that runs at 03:00; additionally collides with the nightly backup. Context: this Friday, at the end of the fiscal period. Reported by the monitoring system. | Schedule action for this scenario. | scheduling | agent | yuri_v3 |
v3_219a973ac1761c75_c | choice | [
"critical",
"high",
"normal",
"low"
] | [
0.45,
0.29,
0.02,
0.24
] | A maintenance window requires exclusive database access; additionally is idempotent and safe to retry. Context: during peak traffic, mid-incident. Reported by the review queue. | Priority for this scenario. | scheduling | agent | yuri_v3 |
v3_8315939c04e1ac58_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0.01,
0.5,
0.49,
0
] | A maintenance window has a hard customer-facing deadline; additionally depends on a task that runs at 03:00. Context: every 4 hours, while on-call rotation changed. Reported by the operator. | Rate schedule conflict risk for this scenario on a 0-5 scale. | scheduling | agent | yuri_v3 |
v3_1c0d04995a0c820e_c | choice | [
"run_now",
"delay",
"split_window",
"move_to_next_slot"
] | [
0.08,
0.45,
0.14,
0.33
] | The batch job is idempotent and safe to retry; additionally depends on a task that runs at 03:00. Context: on the first of the month, during an external partner integration. Reported by the on-call engineer. | Schedule action for this scenario. | scheduling | agent | yuri_v3 |
v3_39a3994fd91a4af0_n | noul | [
"false",
"true"
] | [
0.75,
0.25
] | The report generation requires exclusive database access; additionally shares a lock with the payroll run. Context: every 4 hours, following a recent audit. Reported by the operator. | Is this scenario one where: retries are safe here? | scheduling | agent | yuri_v3 |
v3_4ec883bf33380f35_n | noul | [
"false",
"true"
] | [
0.78,
0.22
] | The batch job fits entirely inside the quiet period; additionally has run over its window 3 weeks straight. Context: this Friday, during the holiday freeze. Reported by the supervisor. | Is this scenario one where: retries are safe here? | scheduling | agent | yuri_v3 |
v3_9e1c669d19e13869_c | choice | [
"run_now",
"delay",
"split_window",
"move_to_next_slot"
] | [
0,
0.28,
0.13,
0.59
] | A maintenance window needs 4 hours but the window is 90 minutes; additionally fits entirely inside the quiet period. Context: on the first of the month, with a new vendor onboarded. Reported by the on-call engineer. | Schedule action for this scenario. | scheduling | agent | yuri_v3 |
v3_6aef069b8cde7e3e_c | choice | [
"run_now",
"delay",
"split_window",
"move_to_next_slot"
] | [
0.02,
0.22,
0.07,
0.69
] | A maintenance window has a hard customer-facing deadline; additionally collides with the nightly backup. Context: during peak traffic, during the holiday freeze. Reported by the monitoring system. | Schedule action for this scenario. | scheduling | agent | yuri_v3 |
v3_39cf57adc6fedbe3_c | choice | [
"critical",
"high",
"normal",
"low"
] | [
0.09,
0.25,
0.04,
0.62
] | The report generation needs 4 hours but the window is 90 minutes; additionally requires exclusive database access. Context: during peak traffic, during the morning shift. Reported by the operator. | Priority for this scenario. | scheduling | agent | yuri_v3 |
v3_615052f52850eb60_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.02,
0.08,
0.24,
0.39,
0.24,
0.03
] | A model retrain requires exclusive database access; additionally fits entirely inside the quiet period. Context: during peak traffic, at the end of the fiscal period. Reported by the supervisor. | Rate schedule conflict risk for this scenario on a 0-5 scale. | scheduling | agent | yuri_v3 |
v3_db12f4d419ea43b8_n | noul | [
"false",
"true"
] | [
0.67,
0.33
] | A maintenance window fits entirely inside the quiet period; additionally depends on a task that runs at 03:00. Context: on the first of the month, following a recent audit. Reported by the review queue. | Is this scenario one where: the job will miss its deadline? | scheduling | agent | yuri_v3 |
v3_f47709dda731f400_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.12,
0.41,
0.28,
0.18,
0.01,
0
] | The report generation is idempotent and safe to retry; additionally depends on a task that runs at 03:00. Context: on the first of the month, during the morning shift. Reported by the operator. | Rate deadline feasibility for this scenario on a 0-5 scale. | scheduling | agent | yuri_v3 |
v3_871f1e76becf2bc7_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.04,
0.24,
0.41,
0.3,
0.01,
0
] | The report generation is idempotent and safe to retry; additionally depends on a task that runs at 03:00. Context: every 4 hours, under reduced staffing. Reported by the automated check. | Rate deadline feasibility for this scenario on a 0-5 scale. | scheduling | agent | yuri_v3 |
v3_51a79f52ffd6149d_c | choice | [
"run_now",
"delay",
"split_window",
"move_to_next_slot"
] | [
0.14,
0.35,
0.03,
0.48
] | A model retrain fits entirely inside the quiet period; additionally has run over its window 3 weeks straight. Context: this Friday, at the end of the fiscal period. Reported by the review queue. | Schedule action for this scenario. | scheduling | agent | yuri_v3 |
v3_835411ed356063eb_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.01,
0.15,
0.55,
0.28,
0.01
] | The batch job fits entirely inside the quiet period; additionally collides with the nightly backup. Context: every 4 hours, with staffing at reduced levels. Reported by the automated check. | Rate deadline feasibility for this scenario on a 0-5 scale. | scheduling | agent | yuri_v3 |
v3_b26ffd1962eb4701_n | noul | [
"false",
"true"
] | [
0.96,
0.04
] | The batch job shares a lock with the payroll run; additionally needs 4 hours but the window is 90 minutes. Context: during peak traffic, during the quarterly review. Reported by the operator. | Is this scenario one where: this window is safe? | scheduling | agent | yuri_v3 |
v3_adad947ea7e33be6_n | noul | [
"false",
"true"
] | [
0.47,
0.53
] | The batch job depends on a task that runs at 03:00; additionally requires exclusive database access. Context: on the first of the month, while on-call rotation changed. Reported by the operator. | Is this scenario one where: the job will miss its deadline? | scheduling | agent | yuri_v3 |
v3_18583a6ddd6a9146_c | choice | [
"run_now",
"delay",
"split_window",
"move_to_next_slot"
] | [
0.19,
0.28,
0.07,
0.46
] | The batch job collides with the nightly backup; additionally fits entirely inside the quiet period. Context: during peak traffic, during a scheduled maintenance window. Reported by the automated check. | Schedule action for this scenario. | scheduling | agent | yuri_v3 |
v3_0f3871a49c74004a_c | choice | [
"run_now",
"delay",
"split_window",
"move_to_next_slot"
] | [
0.01,
0.26,
0.1,
0.63
] | The batch job requires exclusive database access; additionally has run over its window 3 weeks straight. Context: during peak traffic, during an external partner integration. Reported by the on-call engineer. | Schedule action for this scenario. | scheduling | agent | yuri_v3 |
v3_b8d962b764d7e06a_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.05,
0.2,
0.28,
0.38,
0.08,
0.01
] | The report generation requires exclusive database access; additionally is idempotent and safe to retry. Context: this Friday, following a recent audit. Reported by the automated check. | Rate deadline feasibility for this scenario on a 0-5 scale. | scheduling | agent | yuri_v3 |
v3_dbd7ea933c9cb2c9_c | choice | [
"run_now",
"delay",
"split_window",
"move_to_next_slot"
] | [
0.21,
0.13,
0.27,
0.39
] | A model retrain depends on a task that runs at 03:00; additionally has a hard customer-facing deadline. Context: on the first of the month, with staffing at reduced levels. Reported by the supervisor. | Schedule action for this scenario. | scheduling | agent | yuri_v3 |
v3_07b854a92e33c08b_n | noul | [
"false",
"true"
] | [
0.8,
0.2
] | A model retrain has a hard customer-facing deadline; additionally has run over its window 3 weeks straight. Context: this Friday, at the end of the fiscal period. Reported by the operator. | Is this scenario one where: retries are safe here? | scheduling | agent | yuri_v3 |
v3_219a973ac1761c75_n | noul | [
"false",
"true"
] | [
0.33,
0.67
] | A maintenance window requires exclusive database access; additionally is idempotent and safe to retry. Context: during peak traffic, mid-incident. Reported by the review queue. | Is this scenario one where: retries are safe here? | scheduling | agent | yuri_v3 |
v3_252749b7fad78e78_n | noul | [
"false",
"true"
] | [
0.79,
0.21
] | The batch job collides with the nightly backup; additionally has a hard customer-facing deadline. Context: this Friday, with staffing at reduced levels. Reported by the operator. | Is this scenario one where: retries are safe here? | scheduling | agent | yuri_v3 |
v3_c5fc101bbb31c602_n | noul | [
"false",
"true"
] | [
0.18,
0.82
] | The batch job is idempotent and safe to retry; additionally has run over its window 3 weeks straight. Context: during peak traffic, as part of a compliance sweep. Reported by the operator. | Is this scenario one where: the job will miss its deadline? | scheduling | agent | yuri_v3 |
v3_7be0227eab2f92d4_n | noul | [
"false",
"true"
] | [
0.06,
0.94
] | The batch job needs 4 hours but the window is 90 minutes; additionally shares a lock with the payroll run. Context: every 4 hours, under reduced staffing. Reported by the automated check. | Is this scenario one where: the job will miss its deadline? | scheduling | agent | yuri_v3 |
v3_8a43d58f74f91f02_n | noul | [
"false",
"true"
] | [
0.85,
0.15
] | The batch job needs 4 hours but the window is 90 minutes; additionally fits entirely inside the quiet period. Context: this Friday, under reduced staffing. Reported by the monitoring system. | Is this scenario one where: retries are safe here? | scheduling | agent | yuri_v3 |
v3_eb58ba27d57855df_n | noul | [
"false",
"true"
] | [
0.8,
0.2
] | The report generation requires exclusive database access; additionally depends on a task that runs at 03:00. Context: this Friday, while on-call rotation changed. Reported by the review queue. | Is this scenario one where: retries are safe here? | scheduling | agent | yuri_v3 |
v3_b641bfb65410d1b6_c | choice | [
"run_now",
"delay",
"split_window",
"move_to_next_slot"
] | [
0.02,
0.25,
0.02,
0.71
] | A model retrain fits entirely inside the quiet period; additionally needs 4 hours but the window is 90 minutes. Context: on the first of the month, following a recent audit. Reported by the monitoring system. | Schedule action for this scenario. | scheduling | agent | yuri_v3 |
v3_277341db911306e1_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.08,
0.34,
0.3,
0.23,
0.04,
0.01
] | A model retrain fits entirely inside the quiet period; additionally is idempotent and safe to retry. Context: this Friday, under reduced staffing. Reported by the supervisor. | Rate deadline feasibility for this scenario on a 0-5 scale. | scheduling | agent | yuri_v3 |
v3_9bea8db8bb3313d3_c | choice | [
"run_now",
"delay",
"split_window",
"move_to_next_slot"
] | [
0.23,
0.11,
0.44,
0.22
] | The batch job has a hard customer-facing deadline; additionally shares a lock with the payroll run. Context: this Friday, immediately after go-live. Reported by the supervisor. | Schedule action for this scenario. | scheduling | agent | yuri_v3 |
v3_eff06fa3b53eb642_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.02,
0.79,
0.19
] | The batch job collides with the nightly backup; additionally shares a lock with the payroll run. Context: during peak traffic, during a scheduled maintenance window. Reported by the automated check. | Rate schedule conflict risk for this scenario on a 0-5 scale. | scheduling | agent | yuri_v3 |
v3_58a94e50428ad6d9_n | noul | [
"false",
"true"
] | [
0.76,
0.24
] | A model retrain has a hard customer-facing deadline; additionally depends on a task that runs at 03:00. Context: every 4 hours, mid-incident. Reported by the on-call engineer. | Is this scenario one where: this window is safe? | scheduling | agent | yuri_v3 |
v3_60b47d783a78ec1c_c | choice | [
"critical",
"high",
"normal",
"low"
] | [
0.5,
0.49,
0,
0.01
] | The batch job needs 4 hours but the window is 90 minutes; additionally collides with the nightly backup. Context: during peak traffic, as part of a compliance sweep. Reported by the supervisor. | Priority for this scenario. | scheduling | agent | yuri_v3 |
v3_6abee6964ac2d16a_n | noul | [
"false",
"true"
] | [
0.06,
0.94
] | The report generation needs 4 hours but the window is 90 minutes; additionally requires exclusive database access. Context: every 4 hours, during the holiday freeze. Reported by the supervisor. | Is this scenario one where: the job will miss its deadline? | scheduling | agent | yuri_v3 |
v3_5584538b74440879_c | choice | [
"run_now",
"delay",
"split_window",
"move_to_next_slot"
] | [
0.22,
0.19,
0.09,
0.5
] | A maintenance window can run on any replica; additionally depends on a task that runs at 03:00. Context: on the first of the month, as part of a compliance sweep. Reported by the operator. | Schedule action for this scenario. | scheduling | agent | yuri_v3 |
v3_0b19cc1d5c8821a0_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.1414,
0.2828,
0.2828,
0.1919,
0.0808,
0.0202
] | A model retrain is idempotent and safe to retry; additionally fits entirely inside the quiet period. Context: this Friday, during peak load. Reported by the automated check. | Rate schedule conflict risk for this scenario on a 0-5 scale. | scheduling | agent | yuri_v3 |
End of preview. Expand in Data Studio
JEV corpus - scheduling
9,670 typed calibrated decision rows from the jev-distill-corpus-v3 corpus (domain: scheduling).
Each row is one typed decision: kind (noul / choice / score), a state, a question, options, and a target probability distribution over the options.
Part of the per-domain split of SargeDev/jev-distill-corpus-v3 - the full corpus in one repo.
Domains:
- Downloads last month
- 42