adam/procurement-ingest
1
0
Fork 0
mirror of https://github.com/Sea-Haven-Industries/procurement-ingest.git synced 2026-10-06 15:41:57 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
procurement-ingest/lambdas/po/email_processor/tests/fixtures/ai-fallback/non-coupa-02.eml

214 lines
11 KiB
Text
Raw Normal View History

feat: template-first PO parser with fail-closed gate and Bedrock fallback (#105) * Add deterministic template parser for WO emails The workorder-email-processor sends every one of ~22.9k emails/month to an LLM, but ~93.6% are the plain-text "AMAZON UPDATE WO DETAILS" comment template and ~6.4% the HTML "AMAZON assign Work Order" template. Parse those two shapes deterministically, offline, so the AI call is reserved for the long tail. The module is pure (no boto3, no network). try_deterministic_parse classifies by subject, extracts the shared contract fields, and returns a result ONLY when it passes a strict fail-closed validation gate: exact contract-key set, subject/id agreement, the literal "Work Order: <id>" double space, per-type required fields, site-code shape, and a label-bleed guard so a value that over-ran into the next field fails. Any miss, drift, or extractor exception yields None so the caller falls back to the AI extractor -- data is never corrupted, only the fallback rate rises. Refs: #23 * Migrate WO processor to Bedrock and fix comment_id collision Switch the AI path from the Anthropic SDK to bedrock-runtime InvokeModel on the inference profile us.anthropic.claude-haiku-4-5-20251001-v1:0 (BEDROCK_MODEL_ID env), so parsing no longer needs a provider API key or Secrets Manager secret. The EXTRACTION_PROMPT and JSON contract are kept byte-identical, so the AI-fallback output is unchanged. Try the new deterministic template parser first and only call Bedrock on a miss/invalid result. Fix issue #23: the WorkOrderComments range key was work_order_id#<comment_time>, so two emails on one WO with an identical or absent comment time collided and overwrote each other. Derive a 12-hex suffix from the S3 object key alone -- deterministic, so an async retry of the same object is byte-identical (idempotent) while distinct emails get distinct keys -- and keep wall-clock now() out of the key (literal 'nocomment' segment when comment_time is absent). Also emit one CloudWatch EMF line per record (Seahaven/WorkorderIngest ParseOutcome, dimensioned by ParseMethod/TemplateId) for parse-outcome observability, replace the deprecated datetime.utcnow() with datetime.now(timezone.utc), and drop the anthropic dependency. Refs: #23 * Migrate PO processor to Bedrock Switch the PO email processor's AI extraction from the Anthropic SDK to bedrock-runtime InvokeModel on the inference profile us.anthropic.claude-haiku-4-5-20251001-v1:0 (BEDROCK_MODEL_ID env), so it no longer needs a provider API key or Secrets Manager secret. PO parsing stays fully AI -- only the provider changes. The EXTRACTION_PROMPT is kept byte-identical and the Bedrock text output is still decoded with json.loads(..., parse_float=Decimal), which DynamoDB requires (it rejects floats). Replace the deprecated datetime.utcnow() with datetime.now(timezone.utc) and drop the anthropic dependency. * Grant Bedrock IAM, drop Anthropic secrets, add fallback alarm Both stacks moved their processors from the Anthropic API to the Bedrock inference profile us.anthropic.claude-haiku-4-5-20251001-v1:0. Grant each processor role bedrock:InvokeModel + bedrock:InvokeModelWithResponseStream on BOTH the inference-profile ARN AND the per-region foundation-model ARNs for us-east-1/us-east-2/us-west-2 (empty-account) -- the us.* profile routes cross-region, so a profile-only grant AccessDenies at runtime. Remove both anthropic-api-key Secret constructs, their grant_read, and the ANTHROPIC_API_KEY_SECRET_ARN env; add BEDROCK_MODEL_ID. The secrets had RemovalPolicy.RETAIN so they are orphaned, not deleted -- flagged in the README for manual post-deploy deletion and key revocation. Add the workorder-email-processor-template-fallback-rate alarm: a FILL(0) + >=10-sample volume-floor MathExpression over the EMF ParseOutcome metric (15-min periods) that pages when the AI-fallback share exceeds 15% sustained, catching Hexagon template drift. ALARM-only SnsAction to site-alerts, no OK action, NOT_BREACHING, matching the existing stack idiom. * Add offline WO parser test suite Cover the deterministic parser with golden-file tests over 55 real scrubbed .eml fixtures (both comment sub-shapes, username Submitted-By, address present/absent, br+CRLF assign addresses), fail-closed validation-gate rules, adversarial and prompt-injection cases that must route to ai_fallback or parse without corrupting other fields, the issue #23 comment_id idempotency invariants, and the Bedrock-fallback dispatch plus EMF-metric emission with a mocked invoke_model. Extend pytest.ini testpaths to discover the co-located suite, and update tests/conftest.load_handler to put a handler's own directory on sys.path so the WO handler's new `from template_parser import ...` resolves under the existing shared handler tests. Point test_local.py at the new template-first + Bedrock flow. Refs: #23 * Document Bedrock migration and WO parse flow in README Record the provider switch to the Bedrock inference profile (no Anthropic API key or Secrets Manager secret, with the retired secrets flagged for manual deletion), the WO deterministic-template-first + AI-fallback flow, the new ParseOutcome EMF metric and template-fallback-rate alarm, the issue #23 comment_id format change, the +00:00 aware-UTC timestamp shift, and offline test instructions. Refs: #23 * Fix f-string lint and formatting in backfill scripts Drop the f prefix from two f-strings that carry no placeholders (F541) and apply ruff format, so `ruff check` / `ruff format --check` pass in CI. * Emit ParseMethod-only EMF set so fallback alarm can fire The fallback-rate alarm queries the ParseOutcome series keyed on ParseMethod alone, but the emitter published only the joint (ParseMethod, TemplateId) dimension set. CloudWatch materializes exactly the listed dimension sets and does not auto-aggregate, so the alarm's series never received data: it evaluated a constant 0 and could never page on template-drift coverage collapse. Publish both ["ParseMethod"] and ["ParseMethod","TemplateId"] and update the EMF regression test to assert both sets are present. * Commit WO parser .eml fixtures for executable coverage The parser test suite globbed for input .eml fixtures that the repo's `*.eml` ignore rule kept uncommitted, so every parametrized golden and fail-closed test collected zero cases and CI could not exercise the deterministic parser that handles 100% of WO email volume. Add a fixtures-only negation to .gitignore and commit the 55 scrubbed positive samples (50 update-plaintext, 5 assign-html) plus 14 ai-fallback and 3 adversarial fixtures. The ai-fallback set covers each fail-closed reason code (subject_no_match, single_space_work_order, malformed_site_code, label_bleed, creation_time_unparseable, wo_id_mismatch, missing_required_field) and the adversarial set proves the parser is total and confines prompt-injection payloads to comment_text without steering the structured fields. * feature: Add PO template parser scaffold and design doc Mirror WO PR #99's template-first approach for the Coupa PO processor. Two templates identified from a full 3,448-email triage: - coupa_new_po (95.5%): scaffolded; fails closed to the LLM until extract_new_po lands. - coupa_cancellation (2.9%): implemented. Nested contract with recursive validation, Decimal money, and a fail-closed gate. Derived fields (site_code/trade/fiscal_year) are deferred to a shared post-stage. Comments, revisions, multi-line, and non-USD emails fall back to Bedrock. docs/po-template-parser.md records the investigation, decisions, and remaining work. Signed-off-by: Adam Moussa <166072409+amoussa1229@users.noreply.github.com> * Implement PO new_po extraction and value-level gate Replace the extract_new_po scaffold stub with the full section-windowed extractor (duplicate-label anchoring, sentinel ship-to, label-keyed U+2022 bullet split, Decimal money from three anchored contexts only) and add value-level gate rules V1-V13. Both new_po_not_implemented scaffold guards are removed; rules 6-8 (unrecognized_status, multiline_unsupported, non_usd) go live. The gate re-derives every byte proof from the email body so an extractor bug cannot vouch for itself: amount re-serialization with a digit/comma border check (the thousands-separator truncation kill switch), sum(lines)==total against both Total blocks, anchor/supplier identity proofs, USPS address shape on the raw pre-enrichment zip, bullet label discipline, and sentinel/artifact hygiene. Any failure falls closed to the LLM; a validation failure is never a parsed result. Refs: #99 * Wire template-first parse into PO handler with EMF metric Run try_deterministic_parse ahead of the Bedrock extractor and fall back only on a miss/invalid (fail-closed) result. The shared enrich_parsed post-stage and the save_cancellation/save_revision/ save_new_po routing are untouched, so both paths write identical DynamoDB shapes and the po-ingest-site-extractor stream contract is preserved. Each record emits one ParseMethod EMF line (Seahaven/PoIngest/ ParseOutcome, dimension sets [ParseMethod] and [ParseMethod,TemplateId], ReasonCode/po_number ride-alongs) mirroring the WO idiom. The metric fires before the Bedrock call so a Bedrock-side error still records the ai_fallback outcome. Refs: #99 * Add PO fallback-rate alarm retuned for ~57 emails/day The WO alarm's 15-min period and >=10-sample floor assume ~760/day and would be structurally dead at PO volume (a 15-min period holds ~0.6 emails, so the floor is never met). Retune: 6-hour periods (~14.25 expected emails), IF((fb+tmpl)>=8,...) volume floor so a single email can never breach a datapoint (1/8 = 12.5% < 20%), threshold >20% against a ~1% expected baseline, eval 4 / datapoints 2 (24h span) so noise self-clears while total template drift pages within ~12h. No element-wise MAX in the math expression (post-#102 rule); ALARM-only SnsAction to site-alerts, NOT_BREACHING. Gated with 'npx cdk synth po-ingest'. Also add template_parser.py to the bundling cp list -- without it every deployed invocation would ImportError (unit tests cannot catch an asset-bundling omission). Refs: #99, #102 * Add offline PO parser suite with scrubbed fixture corpus 132 tests: golden-file comparison for all 25 positive fixtures (17 single-line new-PO + 8 cancellations, Decimal-exact via parse_float=Decimal), every fail-closed gate reason code covered (body-level triggers via 17 synthetic adversarial .eml mutations, candidate-level via direct validate() unit tests), real multi-line and comment/non-Coupa fallback fixtures, dual line-ending parse identity, two-path enrich/save parity (site-extractor stream guard), V10 URL-id corpus sweep, fixture hygiene (ses_auth pass + scrub-marker leak sweep), and Bedrock dispatch/EMF assertions. The suite loads handler/template_parser via importlib under unique module names and binds the handler's bare sibling imports around exec (tests/conftest.py load_handler gets the same treatment) -- the WO suite caches bare 'handler'/'template_parser' names in sys.modules, and bare imports here would silently bind to the wrong pipeline. moto is imported before the handler so its botocore stubber hook precedes boto3 session creation (the PO conftest chain now loads at pytest session start). Fixtures are scrubbed real S3 samples: transport/auth header values replaced with same-shape placeholders (structure kept so ses_auth still passes), per-file digit ciphers, amounts remapped with sum==total re-established. The .gitignore exception is scoped to the PO fixtures path only. Refs: #99 * Document PO template-first parser and retuned alarm README: PO flow is now template-first with Bedrock fallback; parser/gate section mirroring the WO writeup; Seahaven/PoIngest ParseOutcome namespace and the fallback-rate alarm numbers with their volume justification (deliberately not WO's settings); test-suite and repo-layout updates. Design doc: mark PR #1 complete in progress/checklist sections; document the six value-level gate reason codes and the scaffold guard removal; correct the stale data-access note (default CLI session is 328440206208) and note the ~90-day S3 lifecycle aging of the corpus; record the 2.3 layout addendum (leading Supplier bullet segment, EA evidence lines, summary unit-price tokens, decode-path line endings), the fixture-build pins (address join convention, quantity/unit/price source), the V10 sweep outcome, and resolutions for open questions Q3/Q6. Cross-family review and the Confluence architecture-map update are flagged outstanding for merge. Refs: #99 * Record cross-family review outcome for handler wiring GPT-4.1 cross_review.py run against the real handler diff returned no BLOCK and no security findings; both FIX items verified as no-change-needed (fallback logging already correct; non-dict AI output is the pre-existing issue #101 pattern this PR deliberately does not touch). Refs: #99 * Pin line-item currency to USD in the PO gate The non_usd rule only checked the Total-block top-level currency, so a new_po whose line item read 'for 55,206.00 CAD' under a USD Total block still template-parsed as ok -- a fail-open hole in the fail-closed gate. Every line item's captured currency and its re-derived body token must now byte-equal the proven-USD top-level currency; covered by a line-level CAD adversarial fixture (the existing adv-non-usd only exercised the Total-block variant) and a candidate-mutation unit test. * Scrub residual transport tokens from PO fixtures The first-pass harvest scrub sanitized only the primary SES/DKIM header blocks, leaving the real SES Feedback-ID sender-identity hash in 49 committed fixtures and, on the two non-Coupa fixtures, an embedded second SES block's X-Ses-Receipt, the Exchange cross-tenant UPN ciphertext, and Gmail ARC fh= / X-Gm-* tokens -- exactly the token classes the PR #99 fixture lesson requires placeholdered. Replace each with a same-shape ScrubbedFixture value (byte-safe, CRLF and folding preserved) so header structure and ses_auth behavior are unchanged. * Converge quantity/price to Decimal on both paths EXTRACTION_PROMPT declares quantity and price as JSON strings, so a prompt-obedient Bedrock response stores DynamoDB Strings where the template parser stores Numbers -- divergent attribute types for the same email on the purchase-orders stream. Coerce numeric strings to Decimal in the shared enrich_parsed post-stage (thousands-separator safe; non-numeric strings kept verbatim) so both paths converge; prompt rewording itself remains PR #2 scope. The two-path parity test was circular -- it replayed the parser- derived golden as 'the LLM output', so it could never see the type divergence. It now feeds a prompt-shaped payload (string quantity/ price, LLM-filled site_code) through enrich_parsed and save_new_po, and the fixture-hygiene test now asserts the scrubbed transport-token header classes so fixture regressions are caught. * Coerce bare-int quantity/price to Decimal in enrich_parsed GPT-4.1 cross-family review of the final PR diff (no BLOCK) flagged residual type drift: parse_float=Decimal rules out floats on the LLM path, but a bare JSON int survived as Python int. Coerce it so both parse paths emit one canonical Decimal type. * Scrub fixture-body PII and harden cancellation gate (sec review) /sh-security-review of PR #105 (5 fresh-context detectors + proof-or-kill verifier) confirmed two diff-introduced findings; both fixed here. F3 (medium, real PII in new fixtures): the harvest scrub replaced header tokens but left real third-party PII in message BODIES -- an Amazon contact's name/phone/personal email in non-coupa-02.eml and an internal t.corp.amazon.com ticket URL in comment-02.eml, plus real submitter/attn names recurring across the new_po corpus. Replaced every personal name, phone, personal email, and internal URL with synthetic placeholders (QP-soft-wrap aware) across both .eml bodies and expected goldens. Extended test_fixture_hygiene to scan BODIES (phone shapes, corp URLs, the leaked tokens), closing the header-only gap that let this through. F1 (medium, cancellation gate): _CANCELLATION_SUBJECT was unanchored and matched with .search(), unlike the anchored new_po pattern -- a subject merely ending with the cancellation phrase could be routed to the sticky- Cancelled write. Fully anchored it and switched to .match, and added a body-corroboration gate (the real Coupa body independently restates 'Purchase Order #<po> ... has been cancelled'); a near-miss/misrouted subject whose body does not corroborate now fails closed to the LLM (new reason code cancellation_body_unconfirmed). Pre-existing (advisory, not this PR): the LLM-fallback else->save_new_po dispatch and undelimited extraction prompt (issue #101 family) are byte-identical to main and unchanged here. 401 tests pass; ruff/format clean; cdk synth po-ingest clean. --------- Signed-off-by: Adam Moussa <166072409+amoussa1229@users.noreply.github.com>
2026-07-16 17:50:59 -04:00
Return-Path: <info@seahavenind.com>
Received: from mail-ej1-f48.google.com (mail-ej1-f48.google.com [203.0.113.25])
by inbound-smtp.us-east-1.amazonaws.com with SMTP id fixture0123456789fixture0123456789fixtur
for amazon_po@int.seahaven.com;
Wed, 17 Jun 2026 20:27:22 +0000 (UTC)
Received-SPF: pass (spfCheck: domain of seahavenind.com designates 203.0.113.25 as permitted sender) client-ip=203.0.113.25; envelope-from=info@seahavenind.com; helo=mail-ej1-f48.google.com;
Authentication-Results: amazonses.com;
spf=pass (spfCheck: domain of seahavenind.com designates 203.0.113.25 as permitted sender) client-ip=203.0.113.25; envelope-from=info@seahavenind.com; helo=mail-ej1-f48.google.com;
dkim=pass header.i=@seahavenind.com;
dmarc=pass header.from=seahavenind.com;
X-SES-RECEIPT: ScrubbedFixturePlaceholderTokenValue0123456789QqZzXxJjKkWwYyVvScrubbedFixturePlaceholderTokenValue0123456789QqZzXxJjKkWwYyVvScrubbedFixturePlaceholderTokenValue0123456789QqZzXxJjKkWwYyVvScrubbedFixturePlaceholderTokenValue0123456789QqZzXxJjKkWwYyVvScrubbedFixturePlaceholderTokenValue0123456789QqZzXxJjKkWwYyVvScrubbedFixturePlaceholderTokenValue0123456789QqZzXxJjKkWwYyVvScrubbedFixturePlaceholderTokenValue0123456789==
X-SES-DKIM-SIGNATURE: a=rsa-sha256; q=dns/txt; b=Scr/ubbedFixtu+r+ePlaceholderTokenValue0123456789QqZzXxJjKkWwYyVvScrubbedFixturePlaceholderTokenValue0123456789QqZzXxJjKkWwYyVvScrubbedFixtur+ePlaceholderTokenValue0123456=; c=relaxed/simple; s=224i4yxa5dv7c2xz3womw6peuasteono; d=amazonses.com; t=1781728043; v=1; bh=Scr+ubbedFixturePlaceholderTokenVa/lue01234=; h=From:To:Cc:Bcc:Subject:Date:Message-ID:MIME-Version:Content-Type:X-SES-RECEIPT;
Received: by mail-ej1-f48.google.com with SMTP id fixture012345-6789fixture0123456789f.i
for <amazon_po@int.seahaven.com>; Wed, 17 Jun 2026 13:27:22 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1781728041; cv=none;
d=google.com; s=arc-20240605;
b=ScrubbedFixturePlac+eholderTokenValue0123456789QqZzX/xJjKkWwYyVvSc
rubbedFixturePlaceholderTokenValue0123456789QqZzXxJjKkWwYyVvScrubbed
FixturePlaceholderTokenValue0123456789QqZzX+xJjKkWwYyVvScrubbedFixtu
rePlaceholderTokenValue/012345+6789QqZzXxJjKkWwYyVvScrubbedFixt/ureP
l/aceholderTokenValue0123456789QqZzXxJjKkWwYyVvScrubbedFixturePlaceh
/+ol==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605;
h=cc:to:subject:message-id:date:from:in-reply-to:references
:mime-version:dkim-signature;
bh=Scr+ubbedFixturePlaceholderTokenVa/lue01234=;
fh=ScrubbedFixturePlaceholderTokenValue0123456=;
b=ScrubbedFixturePlaceholderTokenValue0123456789QqZzXxJjKkWwYyVvScru
bbedFixtur+ePlaceholderTokenValue0123456789QqZzXxJjKkWwYyVvScrubbedF
ixturePlacehol+derTokenValue0123456789QqZ+z/XxJjKkWwYyVvS+crubb/edFi
xturePlaceholderTokenValue0123456789QqZzXxJjKkWwYyVvScrubbedFixtureP
laceholderTokenValue0123456789QqZzXxJjKkWwYyVvScrubbedFixturePlaceho
lder==;
darn=int.seahaven.com
ARC-Authentication-Results: i=1; mx.google.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=seahavenind.com; s=google; t=1781728041; x=1782332841; darn=int.seahaven.com;
h=cc:to:subject:message-id:date:from:in-reply-to:references
:mime-version:from:to:cc:subject:date:message-id:reply-to;
bh=Scr+ubbedFixturePlaceholderTokenVa/lue01234=;
b=ScrubbedFixturePlaceholderT/okenValue0123456789QqZzXxJ+jKkWwYyVvSc
ru+bbedFixturePl/aceholderToke/nValue0123456789QqZ+zXxJjKkWwYyVv/Scr
ubbedFixturePlace/holderTokenValue012=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20251104; t=1781728041; x=1782332841;
h=cc:to:subject:message-id:date:from:in-reply-to:references
:mime-version:x-gm-gg:x-gm-message-state:from:to:cc:subject:date
:message-id:reply-to;
bh=Scr+ubbedFixturePlaceholderTokenVa/lue01234=;
b=ScrubbedFi+xturePlaceholderTokenValue0123456789+QqZzXxJjKk/WwYyV+v
ScrubbedFixturePlaceholderT/okenValue01234567+/89QqZzXxJjKkWwYyVvSc/
ru+bbedFixturePlaceholderTokenValue0123456789Q/q+/Zz+XxJ/jKkWwYy+V/v
ScrubbedFixturePlaceholderTokenValue0123456789QqZzXxJjKkWwYyVvScrubb
edFixturePlaceholderTokenValue0123456789QqZ+zXxJjKkWwYyVvScrubbedFix
t+ur==
X-Forwarded-Encrypted: i=1; ScrubbedFixturePlaceholderTokenValue0123456789QqZzXxJjKkWwYyVvScrubbedFixturePlaceh=@int.seahaven.com
X-Gm-Message-State: ScrubbedFixturePlaceholderTokenValue0123456789QqZzXxJjKk
ScrubbedFixturePlaceholderTokenValue0123456789QqZzXxJjKkWwYyVvScrubbedFixtu
ScrubbedFixturePlaceholderTokenValue012345678
X-Gm-Gg: ScrubbedFixturePlaceholderTokenValue0123456789QqZzXxJjKkWwYyVvScrub
ScrubbedFixturePlaceholderTokenValue0123456789QqZzXxJjKkWwYyVvScrubbedFixtu
ScrubbedFixturePlaceholderTokenValue0123456789QqZzXxJjKkWwYyVvScrubbedFixtu
ScrubbedFixturePlaceholderTokenValue0123456789QqZzXxJjKkWwYyVvScrubbedFixtu
ScrubbedFixturePlaceholderTokenValue0123456789QqZzXxJjKkWwYyVvScrubbedFixtu
ScrubbedFixt=
X-Received: by 2002:a17:907:9617:b0:bed:7f50:c724 with SMTP id
ScrubbedFixturePlaceholderTokenValue0123456789QqZzXxJj; Wed, 17 Jun 2026
13:27:21 -0700 (PDT)
MIME-Version: 1.0
References: <user238@DS5PR18MB927692.namprd18.prod.outlook.com>
In-Reply-To: <user238@DS5PR18MB927692.namprd18.prod.outlook.com>
From: Sea Haven Main <info@seahavenind.com>
Date: Wed, 17 Jun 2026 16:27:09 -0400
X-Gm-Features: ScrubbedFixturePlaceholderTokenValue0123456789QqZzXxJjKkWwYyVvS
Message-ID: <abcdef0123456789abcdef0123456789ab_cdef0123456789+a@mail.gmail.com>
Subject: =?UTF-8?Q?Re=3A_DJZ5_=2D_Request_for_Service_Completion_=E2=80=93_PO_=232D?=
=?UTF-8?Q?=2D14783046?=
To: "Fixtonly, Pat [C]" <user239@amazon.com>
Cc: "adam@seahavenind.com" <adam@seahavenind.com>,
"amazon_po@int.seahaven.com" <amazon_po@int.seahaven.com>, "O'Donohue, Joe [C]" <user650@amazon.com>,
"Hastrup, Richard" <user172@amazon.com>
Content-Type: multipart/alternative; boundary="000000000000f8b7a4065478e2c5"
--000000000000f8b7a4065478e2c5
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Good Afternoon Pat-
Thank you for your email.
This request was completed back in December of 2025.
I will have our team review this tomorrow, but since it's been six months,
I would imagine the area looks like it was never done specifically due to
the high traffic this site gets.
Daniel
On Wed, Jun 17, 2026 at 4:23=E2=80=AFPM Fixtonly, Pat [C] <user239@amazon.=
com>
wrote:
> Hello Seahaven Team,
>
>
>
> We are reaching out from DJZ5 regarding PO #2D-19542097, which has alread=
y
> been invoiced under invoice #2947938672. However, the associated work has
> not yet been completed.
>
> Could you please dispatch a technician to perform the outstanding work at
> your earliest convenience?
>
> Thank you, and please let us know if any additional information is needed=
.
>
>
>
>
>
>
>
> Pat Fixtonly
>
> Regional Area Maintenance Manager
>
> C&W Services | Amazon
>
> C: (000) 555-0100
>
> E: *user000@amazon.c <user239@amazon.com>om *
>
>
>
--000000000000f8b7a4065478e2c5
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Good Afternoon Pat-<div><br>Thank you for your email.</div=
><div><br></div><div>This request was completed=C2=A0back in December of 20=
25.=C2=A0=C2=A0</div><div><br></div><div>I will have our team review this t=
omorrow, but since it&#39;s been six months, I would imagine the area looks=
like it was never done specifically due to the high traffic this site gets=
.</div><div><br></div><div>Daniel</div><div><br></div></div><br><div class=
=3D"gmail_quote gmail_quote_container"><div dir=3D"ltr" class=3D"gmail_attr=
">On Wed, Jun 17, 2026 at 4:23=E2=80=AFPM Fixtonly, Pat [C] &lt;<a href=3D=
"mailto:user239@amazon.com">user239@amazon.com</a>&gt; wrote:<br></div><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left=
:1px solid rgb(204,204,204);padding-left:1ex"><div class=3D"msg639702525558=
0110033">
<div lang=3D"EN-US" style=3D"overflow-wrap: break-word;">
<div class=3D"m_6397025255580110033WordSection1">
<p class=3D"MsoNormal">Hello Seahaven Team, <u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"m_6397025255580110033isselectedend">We are reaching out from DJ=
Z5 regarding PO #2D-19542097, which has already been invoiced under invoice=
#2947938672. However, the associated work has not yet been completed.<u></=
u><u></u></p>
<p class=3D"m_6397025255580110033isselectedend">Could you please dispatch a=
technician to perform the outstanding work at your earliest convenience?<u=
></u><u></u></p>
<p>Thank you, and please let us know if any additional information is neede=
d.<u></u><u></u></p>
<p><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-size:=
10pt;font-family:&quot;Amazon Ember Display&quot;,sans-serif;color:rgb(31,7=
3,125);border:1pt windowtext;padding:0in">Pat Fixtonly</span><span style=
=3D"font-size:11.5pt;font-family:&quot;Segoe UI&quot;,sans-serif;color:rgb(=
36,36,36)"><u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-size:=
10pt;font-family:&quot;Amazon Ember Display&quot;,sans-serif;color:rgb(31,7=
3,125);border:1pt windowtext;padding:0in">Regional Area Maintenance Manager=
</span><span style=3D"font-size:11.5pt;font-family:&quot;Segoe UI&quot;,san=
s-serif;color:rgb(36,36,36)"><u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-size:=
10pt;font-family:&quot;Amazon Ember Display&quot;,sans-serif;color:rgb(31,7=
3,125);border:1pt windowtext;padding:0in">C&amp;W Services=C2=A0|=C2=A0Amaz=
on</span><span style=3D"font-size:11.5pt;font-family:&quot;Segoe UI&quot;,s=
ans-serif;color:rgb(36,36,36)"><u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-size:=
10pt;font-family:&quot;Amazon Ember Display&quot;,sans-serif;color:rgb(31,7=
3,125);border:1pt windowtext;padding:0in">C: (000) 555-0100</span><span sty=
le=3D"font-size:11.5pt;font-family:&quot;Segoe UI&quot;,sans-serif;color:rg=
b(36,36,36)"><u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-size:=
10pt;font-family:&quot;Amazon Ember Display&quot;,sans-serif;color:rgb(31,7=
3,125);border:1pt windowtext;padding:0in">E:</span><span style=3D"font-size=
:10pt;font-family:&quot;Amazon Ember Display&quot;,sans-serif;color:rgb(68,=
84,106);border:1pt windowtext;padding:0in">=C2=A0</span><u><span style=3D"f=
ont-size:10pt;font-family:&quot;Amazon Ember Display&quot;,sans-serif;color=
:rgb(5,99,193);border:1pt windowtext;padding:0in"><a href=3D"mailto:user239=
@amazon.com" title=3D"mailto:user239@amazon.com" target=3D"_blank"><span st=
yle=3D"color:blue">user000@amazon.c</span></a>om=C2=A0</span></u><span styl=
e=3D"font-size:11.5pt;font-family:&quot;Segoe UI&quot;,sans-serif;color:rgb=
(36,36,36)"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</div>
</div></blockquote></div>
--000000000000f8b7a4065478e2c5--
Reference in a new issue Copy permalink