Let repeated tasks follow a rule Before automating a reminder, spell out when it should and should not happen. What you will make Get a row-by-row simulation explaining the temperature rule. Example result At least 28°C: 2 simulated start requests. Above 28°C: 1 request; repeated events do not trigger again. This is a prepared example. Your AI may use different wording. Follow along Work in your own AI tool Practice material Fictional temperature readings for text simulation; no equipment connection. Rule: at 28°C or above, create one simulated air-conditioner start request and one notification. Below 28°C, do nothing. With no temperature, do nothing for now. If an event ID has already been processed, do not process it again. In order: E01: 27°C; E02: 28°C; E03: 29°C; E04: no temperature; E02: 28°C (the same event sent again). Request for AI Try the rules below. For each row show temperature, whether it produces a simulated start request, whether it notifies, and one reason. Do not process a repeated event twice. Use text simulation only. 1. Paste the rules, five readings, and request into AI to get a trial table. 2. Check that 28 and 29 degrees each produce one request and notification; the missing reading produces no action. 3. Then send: “Change the rule to above 28 degrees and rerun these five events from an empty record.” See whether the 28-degree event stops triggering. 4. Compare the two versions: 2 requests first, then 1. This tests a rule; it does not connect to real equipment. After trying: compare a possible result E01 27: no activation, 0 requests/0 notifications. E02 28: simulated activation, 1/1. E03 29: simulated activation, 1/1. E04 missing: unknown, 0/0. Redelivered E02: skipped, 0 new requests/0 new notifications. Total 2 requests and 2 notifications. A fresh >28 batch activates only E03, total 1; restoring >=28 gives 2. Comparison and deduplication are rules; AI can help write and explain them. No actual device was controlled. Check these parts of your result At least 28 includes 28; above 28 does not. Missing readings cause no action; repeated event IDs cause no new notification. This is text simulation, not actual air-conditioner control. Try a different situation yourself New fictional rule and events: humidity >=70% produces one dehumidification reminder, simulation only; deduplicate by ID and mark missing as unknown. In order: H01,69; H02,70; H03,71; H04,missing; H02,70 redelivery. List each result independently. H01 no reminder; H02 one; H03 one; H04 unknown, none; duplicate H02 skipped. Total 2 reminders. 70 qualifies; missing is not 0%. Try a more involved task Specify failure retries and cooldown state explicitly. Fictional simulation, Asia/Taipei. Rules: >=28 creates a request; at most 2 attempts per ID including the first; only success marks the event processed and allows notification; persistent failure goes to a person. Other events within 5 minutes after a successful notification may create requests but no notification. R1 at 10:00, 28°C: first attempt fails, retry succeeds 10:01. R1 redelivered 10:02. R2 at 10:03, 29°C: succeeds. R3 at 10:07, 28°C: both attempts fail. Simulate state only. List attempts, success/failure, deduplication, and notifications in order. Do not retry any external service. R1: 2 attempts, succeeds and notifies once at 10:01; redelivery 10:02 skipped. R2: 1 successful attempt, no notification because only 2 minutes have passed. R3: 2 failed attempts, then stop and refer to a person; no success state or success notification. Total 5 attempts, 2 successful events, 1 notification. No unlimited retries. Save your work and continue later Save the AI response in your own notes and add one sentence about what you changed. You can also use the optional record below.