Settings

Settings

Back

Duplicate Prevention

NephAI follows this whenever the situation you described comes up.

EditTry it outWhere it has been usedBack
On

All your work · must follow

Immediately before sending an email, creating an event, or creating a Task, check whether the same action has already occurred. Consider: - Sent messages; - Drafts; - existing Calendar events; - open Tasks; - recently completed Tasks; - actions performed by another Automation; and - actions completed manually by the user. Every external action must have an idempotency mechanism.

What this rule says

Work this covers

Global; email, Calendar, and Tasks

When it kicks in

Immediately before creating an external action or Task

What NephAI does

Immediately before sending an email, creating an event, or creating a Task, check whether the same action has already occurred. Consider: - Sent messages; - Drafts; - existing Calendar events; - open Tasks; - recently completed Tasks; - actions performed by another Automation; and - actions completed manually by the user. Every external action must have an idempotency mechanism.

When NephAI checks it

  • While it gathers information
  • Just before it acts
  • Straight after it acts

Limited to

email · Calendar · Tasks

Your test cases

2 cases you set up to check this reads correctly

If NephAI cannot satisfy it

It holds that piece of work and brings it to you rather than proceeding against this rule.

Try it out

See where this rule would take effect and how NephAI reads the cases you set up. This only shows you the result — nothing is saved, sent, or changed.

Where this rule has been used

Clashes with other rules

0

None. This rule has never asked for something another rule contradicted.

Times NephAI used it

50

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 10, 2026, 12:39 AM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 10, 2026, 12:39 AM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 10, 2026, 12:35 AM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 10, 2026, 12:35 AM

  • Taken into account · Automation occurrence planning

    while gathering information

    Sep 10, 2026, 12:30 AM

  • Taken into account · Automation occurrence planning

    while gathering information

    Sep 10, 2026, 12:24 AM

  • Taken into account · Automation occurrence planning

    while gathering information

    Sep 10, 2026, 12:23 AM

  • Taken into account · Automation occurrence planning

    while gathering information

    Sep 10, 2026, 12:20 AM

  • Taken into account · Automation occurrence planning

    while gathering information

    Sep 10, 2026, 12:19 AM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 10, 2026, 12:15 AM

  • Taken into account · Automation occurrence planning

    while gathering information

    Sep 10, 2026, 12:15 AM

  • Taken into account · Automation occurrence planning

    while gathering information

    Sep 10, 2026, 12:07 AM

  • Taken into account · Automation occurrence planning

    while gathering information

    Sep 10, 2026, 12:07 AM

  • Taken into account · Automation occurrence planning

    while gathering information

    Sep 10, 2026, 12:04 AM

  • Taken into account · Automation occurrence planning

    while gathering information

    Sep 10, 2026, 12:03 AM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 10, 2026, 12:00 AM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 10, 2026, 12:00 AM

  • Taken into account · Automation occurrence planning

    while gathering information

    Sep 9, 2026, 11:59 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 11:48 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 11:46 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 11:43 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 11:41 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 11:33 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 11:31 PM

  • Could not be checked · Task changes

    just before acting · The work was held for you

    Sep 9, 2026, 11:29 PM

  • Taken into account · Task changes

    just before acting

    Sep 9, 2026, 11:29 PM

  • Taken into account · Automation occurrence planning

    while gathering information

    Sep 9, 2026, 11:28 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 11:28 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 11:25 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 11:17 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 11:17 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 11:15 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 11:15 PM

  • Could not be checked · Task changes

    just before acting · The work was held for you

    Sep 9, 2026, 11:13 PM

  • Taken into account · Task changes

    just before acting

    Sep 9, 2026, 11:13 PM

  • Taken into account · Automation occurrence planning

    while gathering information

    Sep 9, 2026, 11:13 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 11:12 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 11:12 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 11:09 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 11:09 PM

  • Taken into account · Automation occurrence planning

    while gathering information

    Sep 9, 2026, 11:01 PM

  • Taken into account · Automation occurrence planning

    while gathering information

    Sep 9, 2026, 11:00 PM

  • Taken into account · Automation occurrence planning

    while gathering information

    Sep 9, 2026, 10:59 PM

  • Followed · Task changes

    just before acting · The work was held for you

    Sep 9, 2026, 10:58 PM

  • Taken into account · Task changes

    just before acting

    Sep 9, 2026, 10:57 PM

  • Taken into account · Automation occurrence planning

    while gathering information

    Sep 9, 2026, 10:57 PM

  • Taken into account · Automation occurrence planning

    while gathering information

    Sep 9, 2026, 10:56 PM

  • Taken into account · Situation assessment

    on an email conversation

    Sep 9, 2026, 10:56 PM

  • Taken into account · Automation occurrence planning

    while gathering information

    Sep 9, 2026, 10:53 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 10:46 PM