Private Preview
Join Waitlist →

Fix over-matching custom patterns

Narrow a custom pattern when it marks too much text or catches the wrong values.

Updated 31 May 20265 min readAuthor: Redactorr Support Team · [email protected]Last reviewed: May 2026

Outcome

You can identify why a pattern over-matches, test a safer version with fake data, and recheck the first real output carefully.

Your progress

Mark each step as you complete it. This is saved only in this browser.

0 / 3 steps complete

Before you start

Use fake examples that include both should-match and should-not-match cases.
Know what the pattern is meant to find.
Keep the original pattern available until the replacement is tested.

Visual frame

Review asset

Custom pattern over-matching storyboard

Synthetic pattern troubleshooting frame only. It explains review behaviour without exposing regex internals or live identifiers.

IssueFalse positives
TestPositive and negative
RolloutManual first run

Synthetic frame

Over-match issue

Describe the wrong catches first.

Should catchSupplier IDs
Catches wronglyOrder numbers
ExampleFake values only
Plain-language diagnosis comes before pattern changes.

Fix over-matching custom patterns workflow frame

Instructional frame for this operational guide. Replace with product screenshots only after the current screen state is approved.

FindName what it catches incorrectly
DecideTest fake positive and negative cases
VerifyReview the first real run carefully

Guided steps

Follow the task, then check the result.

Name what it catches incorrectly

Write down the kind of text being caught by mistake, such as dates, order numbers, product codes, or normal words.

Success check: You can describe the false positive in plain language.

Test fake positive and negative cases

Use synthetic examples that should match and examples that should not match. Adjust until the pattern separates them.

Success check: Fake tests show fewer incorrect matches without losing expected matches.

Review the first real run carefully

Run the adjusted pattern on a real document only after fake tests, then inspect the first result before using bulk actions.

Success check: The adjusted pattern behaves as intended in context.

Branch questions

Completion check

The over-match was described in plain language.
Fake positive and negative cases were tested.
The first real run was reviewed manually.

Support boundary

Support can use by default

  • Article slug and selected workflow step.
  • Screen or action name.
  • Browser, viewport, workspace type, and file type category when relevant.
  • Synthetic sample shape or already-redacted sample only after review.
  • Intent ID
  • Article slug
  • App route

Requires your consent

  • User-written description
  • Email address
  • Explicit attachment
  • Redacted sample
  • Support bundle previewed to the user

Not collected by default

  • Raw original document text
  • Full local file paths
  • Pasted private content
  • Unmasked screenshots
  • Replay capture

Safe support summary

Copy a scrubbed handoff.

Redactorr KB support summary

Article: /knowledge-base/custom-pattern-overmatching
Selected issue: The pattern tester result and Canvas result disagree.
Playbook progress: 0/3 steps marked complete

Safe context to include:
- Article slug and selected workflow step.
- Screen or action name.
- Browser, viewport, workspace type, and file type category when relevant.
- Synthetic sample shape or already-redacted sample only after review.
- Intent ID
- Article slug
- App route

Requires explicit consent:
- User-written description
- Email address
- Explicit attachment
- Redacted sample
- Support bundle previewed to the user

Do not include by default:
- Raw original document text
- Full local file paths
- Pasted private content
- Unmasked screenshots
- Replay capture

User note:
- Describe the step and symptom without pasting raw document text, secrets, files, or restoration material.

Article details

Fix over-matching custom patterns

Narrow a custom pattern when it marks too much text or catches the wrong values.

Use this guide when the custom pattern tester surface is available in your workspace. If you cannot see the screen or control described here, use the safe support path instead of guessing.

Outcome

You can identify why a pattern over-matches, test a safer version with fake data, and recheck the first real output carefully.

Before You Start

  • Use fake examples that include both should-match and should-not-match cases.
  • Know what the pattern is meant to find.
  • Keep the original pattern available until the replacement is tested.

1. Name what it catches incorrectly

Write down the kind of text being caught by mistake, such as dates, order numbers, product codes, or normal words.

Check before you continue: You can describe the false positive in plain language.

2. Test fake positive and negative cases

Use synthetic examples that should match and examples that should not match. Adjust until the pattern separates them.

Check before you continue: Fake tests show fewer incorrect matches without losing expected matches.

3. Review the first real run carefully

Run the adjusted pattern on a real document only after fake tests, then inspect the first result before using bulk actions.

Check before you continue: The adjusted pattern behaves as intended in context.

Completion Check

  • The over-match was described in plain language.
  • Fake positive and negative cases were tested.
  • The first real run was reviewed manually.

Safe Examples

  • ACME-123 should match; ABC should not match.
  • Fake ticket IDs that do not resemble live internal records.

If You Need Support

Contact support when:

  • The pattern tester result and Canvas result disagree.
  • A pattern cannot be narrowed without missing required cases.

Include only support-safe context:

  • Article slug and selected workflow step.
  • Screen or action name.
  • Browser, viewport, workspace type, and file type category when relevant.
  • Synthetic sample shape or already-redacted sample only after review.

Still stuck?

Copy a safe article handoff.

Start support with the article, the issue, and safe context. Raw document text, files, restoration material, and unredacted screenshots stay out unless you explicitly choose otherwise.

Support can start here
  • Article slug
  • Selected issue
  • Screen name
  • Action name
Redactorr support case

Source: Article playbook: custom-pattern-overmatching
Route: /knowledge-base/custom-pattern-overmatching
Selected issue: The pattern tester result and Canvas result disagree.

Safe context:
- Article slug and selected workflow step.
- Screen or action name.
- Browser, viewport, workspace type, and file type category when relevant.
- Synthetic sample shape or already-redacted sample only after review.
- Article slug
- Selected issue
- Screen name or article section
- Action name

Only include with explicit consent:
- User-written description
- Email address
- Explicit attachment
- Redacted sample
- Support bundle previewed to the user

Do not include by default:
- Raw original document text
- Full local file paths
- Pasted private content
- Unmasked screenshots
- Replay capture
- Hidden diagnostic uploads

User note:
- Describe what you tried and what happened. Do not paste raw document text, secrets, files, restoration material, or unredacted screenshots.

Support case builder

One case format, wherever you start.

This is the same support case shape used by diagnostics and article handoffs.

Safe to include
  • Article slug and selected workflow step.
  • Screen or action name.
  • Browser, viewport, workspace type, and file type category when relevant.
  • Synthetic sample shape or already-redacted sample only after review.
  • Article slug
  • Selected issue
Consent boundary

Private material belongs behind an explicit consent step, not in the initial case.

6 default exclusions

Before you copy0/4 ready
Open safe support guide