Three renewal terms were set to end between Sep 27 and Oct 13.

The customer reported SSO login failures affecting everyone using SSO and paused a downstream job pending a response.

for everyone who logs in via SSO: SSO login SAML logins fail with an invalid signature, first noticed at 14:59. We have paused the downstream job until we hear back.

Jennifer Ashford, Security Engineer, Cautera Technologies

Support acknowledged investigation despite new/unassigned ticket metadata, but supplied no diagnosis or recovery result.

We are looking at is there an incident? SAML logins fail with an invalid signature on the Canadian data residency tenant now and will come back to you.

Robert Deepcroft, Tenovia Analytics Support

The customer reported possible workspace-isolation failure in ACH results.

our API integration reports that the ACH batch returns records belonging to a different workspace.

Ana Avonstead, Cautera Technologies customer

The customer described repeated occurrences on an on-premise gateway since a plan upgrade, broadening the reported scope.

Yes, same on our on-premise gateway. It has happened a handful of times since our upgrade to the new plan.

Ana Avonstead, Cautera Technologies customer

Support claimed a rate-limit configuration rollback but requested, rather than received, customer confirmation.

Root cause is a rate-limit misconfiguration on api-gateway, introduced in v1.4.1 and only reachable through /v1/api-gateway/reports. Rolled back in eu-west-1 - could you retry and confirm?

Wei Riverthorpe, Tenovia Analytics support

The latest supplied support update says the bug remained with Tenovia and asserts seasonal-peak blockage.

This is still with us. The internal bug names a rate-limit misconfiguration, and it is prioritised because it blocks the seasonal traffic peak.

Wei Riverthorpe, Tenovia Analytics support

The customer questions two historical degradations; separately, the seller attributes evaluation out-of-memory errors to a release.

your status page had data-warehouse-loader degraded twice last quarter - what changed after that

Ana Avonstead, external Systems Administrator; separate release attribution by Anthony Clayton, internal Account Executive

Security, not price, is the customer's stated procurement gate despite provisional budget.

Security - security review is the gate procurement worries about, not the price, more or less.

Ana Avonstead, external Systems Administrator

The buyer's Q1 statements require separation of present evaluation from future rollout.

Let us keep Q1 out of it for now and talk about what is in front of us.

Ana Avonstead, external Systems Administrator

The seller identifies $197,500 as platform-only and recommends excluding the optional add-on in year one.

The $197,500 is the platform; the add-on is separate and I would not buy it in year one.

Anthony Clayton, internal Account Executive

The seller's 36-month rate explanation conflicts at face value with later unchanged per-seat pricing.

a 36 month term is possible, at a different rate - I will show you - I can check the exact figure.

Anthony Clayton, internal Account Executive

Configuration continuity and an absent adoption baseline are qualification gaps, not established dependency or achieved ROI.

On our side, if Ana leaves, does anyone else at Cautera Technologies know how this is configured?

Nina Moore, external VP Engineering; baseline commitment by Ana Avonstead

Customer reports roughly 43% usage growth, about 171 users with no complaints, adoption ahead of expectations and interest from two additional teams.

Our usage is up roughly 43% on last quarter, which nobody expected.

Ana Avonstead, external Systems Administrator

Customer prefers a 36-month rate lock and conditionally targets the next executive sync; renewal is mentioned as a later point for an unspecified issue.

We would rather sign for 36 months and lock the rate.

Ana Avonstead, external Systems Administrator

Support states that three open tickets share one root cause and should be addressed first.

Between us, honestly, three of your open tickets are the same root cause - I would like to close that first.

Robert Bainton, internal Support Engineer

Seller links an evaluation JSONDecodeError to v1.5.1; the customer's question about detecting the release problem is not substantively answered.

Ana, we shipped v1.5.1 the week you were evaluating, which is where the JSONDecodeError in your logs came from, give or take.

Anthony Clayton, internal Account Executive

Seller's stated 575 ms p95 equals the customer's latency budget; promised 43% tier headroom does not establish support for doubling volume.

Our own p95 budget is 575 ms; where does yours sit under that load?

Ana Avonstead, external Systems Administrator

Seller answers Jira connector ownership/on-call, but later promises another meeting to give the Jira question a real answer.

The Jira connector is ours, and it is on the same on-call as the platform, more or less.

Anthony Clayton, internal Account Executive

Duplicate production notifications created a go-live readiness concern, although the customer explicitly said it was not yet urgent.

Could you check retention policy? It sends the notification twice - error 502, request req_ae3aab1b4e, on production. Not urgent yet, but it becomes urgent at our go-live next week.

Anthony Antonenko, Cautera Technologies Platform Engineer; customer

Richard reported stale production payout configuration with a payroll-cutover dependency.

It applies yesterday's configuration instead of the current one - error 422, request req_1f70e5b27b, on production. Not urgent yet, but it becomes urgent at payroll cutover.

Richard Alderwell, Cautera Technologies end-user

John acknowledged investigation, without a supplied recovery result.

We are looking at payout schedule reading stale configuration on production now and will come back to you.

John Ashwood, Tenovia support

Jessica reported unparsable sanctions-screening exports in the sandbox, with three or four occurrences and error 503.

Reporting this from our sandbox at 16:42: sanctions screening escapes the delimiters so the file cannot be parsed.

Jessica Ashford, Obsidian Partners, Systems Administrator

The customer made stability a requirement before an annual pricing refresh, creating a commercial qualification lead rather than a proven renewal rescue.

We need it stable before the annual pricing refresh - what do you need from us?

Jessica Ashford, Obsidian Partners

Inge acknowledged investigation, but supplied text contains no remediation or customer retest.

We are looking at sanctions screening producing an unparsable export for our warehouse scanners now and will come back to you.

Inge Anderson, Tenovia Support

Customer reports trend-chart adoption ahead of expectations at about 174 users.

Adoption of trend chart is ahead of where we expected - about 174 people are in it now - does that work for you?

Karen Barnshaw (external)

Customer indicates conditional agreement by the next executive sync if the quoted number holds.

Realistically, if you can hold that number we can be done by the next exec sync, more or less.

Karen Barnshaw (external)

Customer places an unspecified issue at a renewal 12 months later, complicating current renewal classification.

We can raise that at renewal in 12 months rather than now.

Jessica Ashford (external)

Seller flags plan rate limits at the reported adoption scale; capacity validation remains open.

One thing to flag: the rate limit on your plan is what 174 users hit first - if that is fair.

Patricia Willowworth (internal)

Karen reports healthy 195-user adoption, with additional teams and the executive sponsor interested in expansion.

We have reconciliation report in front of 195 users now with no complaints.

Karen Barnshaw, external Head of Infrastructure

The seller quotes $161,000 for the platform alone; Karen favors an 18-month rate lock and conditionally targets board-review agreement.

the $161,000 is the platform; the add-on is separate and I would not buy it in year one

Wei Alderton, internal Enterprise Account Executive; related buying statements from Karen Barnshaw, external

The customer discusses renewal 18 months later, while seller references to Q2 require calendar clarification.

We can raise that at renewal in 18 months rather than now.

Karen Barnshaw, external Head of Infrastructure; related timing statements from Wei Alderton, internal

Karen reports two prior-quarter webhook-dispatcher degradations and asks what changed; the seller's incident characterization does not answer that question.

Your status page had webhook-dispatcher degraded twice last quarter - what changed after that?

Karen Barnshaw, external Head of Infrastructure; related response from Wei Alderton, internal

Karen reports roughly 60% quarterly usage growth; seller limit warnings need reconciliation with proposed-tier headroom.

Our usage is up roughly 60% on last quarter, which nobody expected - that is where we are, anyway.

Karen Barnshaw, external Head of Infrastructure; related capacity assertions from Wei Alderton, internal

Karen raises configuration continuity and support-ownership questions, not a confirmed departure or single-admin failure.

Wei, if Karen leaves, does anyone else at Obsidian Partners know how this is configured?

Karen Barnshaw, external Head of Infrastructure, as mapped in the supplied transcript

Customer reported two ledger-export outages since the new fiscal year began.

To be honest, ledger export has been down twice since the new fiscal year started.

David Thompson, external Head of Engineering

Another failure before the board review would undermine the customer's ability to defend the platform.

If ledger export goes down again before the board review I cannot defend this

David Thompson, external Head of Engineering

Customer reported five open tickets and no received ledger-export failure RCA.

I mean, well, wei, five of the tickets we raised are still open, more or less.

David Thompson, external Head of Engineering

Maintenance communication failed to reach the security team before the window began.

nobody told the security team about the last maintenance window until it had started

David Thompson, external Head of Engineering

The us-west-2 entity had to be in scope to clear legal.

Our us-west-2 entity has to be in scope or this does not clear legal.

David Thompson, external Head of Engineering

Wei explicitly offered ownership of the five-ticket escalation and further remediation deliverables.

Well, so - I am escalating all Five of them today and will own the follow-up, subject to the usual caveats.

Wei Irondale, internal Account Executive

Seller quoted $200,500 for the platform and separately questioned quiet seats in a 57-seat discussion.

Look, the $200,500 is the platform; the add-on is separate and I would not buy it in year one.

Wei Irondale, internal Account Executive

The buyer reports board-level alert-rule risk and procurement discussions about an alternative vendor.

Yeah - we have already had the procurement conversation about the other vendor on the shortlist.

David Thompson, external Head of Engineering

David reports five still-open tickets and warns that another alert-rule failure before go-live would be indefensible.

Wei, five of the tickets we raised are still open - that is where we are, anyway.

David Thompson, external Head of Engineering

The buyer asks conditionally about exit if renewal is not taken in 12 months, rather than refusing renewal.

Sure - what does the exit look like if we do not renew in 12 months?

David Thompson, external Head of Engineering

The seller promises a remediation plan and pre-go-live RCA, but no completed recovery is demonstrated.

Right, I will have the alert rule RCA with you before their go-live.

Wei Irondale, internal Account Executive; related engineering assertion by Diego Carrton

The seller identifies $213,500 as platform-only, with the add-on separate and not recommended in year one.

David, the $213,500 is the platform; the add-on is separate and I would not buy it in year one.

Wei Irondale, internal Account Executive

David says another reconciliation-report failure before month end would be indefensible; the seller explicitly frames the discussion as renewal recovery.

The thing is, yeah - if reconciliation report goes down again before the end of the month I cannot defend this.

David Thompson, External, Head of Engineering; Wei Irondale supplies the renewal framing

David reports deteriorating support over six months and internal pressure for another shortlisted vendor.

To be fair, your support times have gone the wrong way for 6 months, and the other vendor on the shortlist is being pushed internally.

David Thompson, External, Head of Engineering

The seller acknowledges a maintenance notice should have reached the customer and promises to investigate its absence.

You should have had the maintenance notice; I will find out why you did not.

Wei Irondale, Internal, Account Executive

The customer makes the month-end write-up a stall gate; Wei promises escalation ownership, a remediation plan and an RCA.

Going back a step, send it before the end of the month or this stalls.

David Thompson, External, Head of Engineering; Wei Irondale makes the recovery commitments

The seller raises 35 seats and quiet users for review before renewal, suggesting a usage qualification lead rather than a confirmed reduction.

The 35 seats and the quiet ones are worth a conversation - not at renewal, now - if that is fair.

Wei Irondale, Internal, Account Executive

Bluepeak reported recurring dispute-form truncation under load and needed stability before a regulator submission deadline.

It has happened about once an hour under load, always with error 500. We need it stable before the regulator's submission deadline - what do you need from us?

Nancy Holmthorpe, Bluepeak Technologies Platform Engineer, customer

Support ultimately pointed to rate-limit misconfiguration and supplied a write-up, not explicit deployment evidence.

The trace for req_22c7d7cd52 points at a rate-limit misconfiguration. I have written it up so you have something for the regulator's submission deadline.

Robert Brentwell, Tenovia Analytics Support

Nancy positively verified no recurrence at the disaster-recovery site on December 7.

Verified on the disaster-recovery site this morning, no recurrence. Thanks for chasing a rate-limit misconfiguration down.

Nancy Holmthorpe, Bluepeak Technologies, customer

The following day's customer email reports the same timeout after the no-recurrence verification.

Another one just now, same sqlx::Error::PoolTimedOut against /v1/data-warehouse-loader/webhooks.

Nancy Holmthorpe, Bluepeak Technologies Platform Engineer, customer

A separate internal note says a Bluepeak review was waiting for an invoice-PDF update.

Bluepeak Technologies review is waiting on an update around invoice PDF

Robert Brentwell, Tenovia Analytics Support, internal note

Bluepeak reported approximately 30-second ACH timeouts affecting about a dozen users.

the ACH batch times out after roughly 30 seconds. about a dozen users are affected.

Nancy Holmthorpe, Bluepeak Technologies Platform Engineer

Support reported a cache-key fix, but the same version label appears in the failing-service and rollout descriptions.

v1.2.1 has the fix and is rolling out now.

Linda Ashwood, Tenovia Analytics Support

The customer explicitly confirmed recovery and authorized closure, first in a comment and then by email.

ACH batch is behaving again on our side. Happy for you to close this.

Nancy Holmthorpe, Bluepeak Technologies Platform Engineer

The customer reported a whole-team login outage, but the later diagnostic thread does not establish the SAML failure's cause.

Reporting an outage for our whole team: SAML logins fail with an invalid signature on SSO login from 08:26 onwards.

Michael Clearwood, Celsara customer; email signature identifies Director of Engineering

Support proposed a slower pagination workaround without customer validation.

A workaround while we dig: call /v1/feature-flags-proxy/sessions one page at a time. Slower, but it has not failed for anybody.

Freya Alderby, Tenovia support agent

Support reported regional mitigation, with permanent repair still promised for a later release.

The mitigation is live in us-west-2; the permanent fix ships with the next release.

Freya Alderby, Tenovia support agent

The final support update still described an unresolved platform escalation.

No change yet - req_d1cc1d6834 is with the platform team and I am chasing it daily.

Freya Alderby, Tenovia support agent

Security, working proof and regulatory residency are customer qualification requirements rather than a price-led rejection.

security review is the gate the platform team worries about, not the price

Mary Bainham, external Security Engineer; residency response by Ravi Avonbourne, internal Senior Account Executive

Budget is approved only in principle; urgency, signoff and timing remain unsettled.

budget is approved in principle by the platform team, but the timing is not fixed

Mary Bainham, external Security Engineer

The seller gives inconsistent descriptions of six-month pricing.

Mary, a 6 month term is possible, at a different rate - I will show you.

Ravi Avonbourne, internal Senior Account Executive

The customer challenges service reliability; seller uptime and retry assurances do not establish remediation.

Sure - your status page had ingest-worker degraded twice last quarter - what changed after that?

Mary Bainham, external Security Engineer; responses by Ravi Avonbourne and Mary Ashbury, internal speakers

The seller attributes an evaluation error to a release; a separate schema diagnosis and integration answer remain unverified.

The thing is, we shipped v1.1.1 the week you were evaluating, which is where the SequelizeDatabaseError in your logs came from.

Ravi Avonbourne, internal Senior Account Executive; schema hypothesis and integration follow-up by Mary Ashbury, internal Platform Engineer

The seller acknowledges product-fit limitations in reporting and chargeback queue maturity.

Where - where I would push back on us: reporting on reopen rate is thinner than Okta's.

Ravi Avonbourne, internal Senior Account Executive

Six-month renewal/exit language coexists with pre-commit evaluation; the exit question is not a refusal to renew.

What does the exit look like if we do not renew in 6 months?

Mary Bainham, external Security Engineer

The buyer identifies security approval, not price, as the CFO's gate; signing authority is still unconfirmed.

Yeah - security review is the gate their CFO worries about, not the price.

Mary Bainham, external Security Engineer

A working alert-rule demonstration and written comparison are required before the decision.

Our platform team will want to see alert rule working before we commit.

Mary Bainham, external Security Engineer

The buyer reports prior service degradations, and the seller separately attributes an evaluation error to a release.

Your status page had etl-pipeline degraded twice last quarter - what changed after that?

Mary Bainham, external Security Engineer; Ravi Avonbourne supplies the release attribution

The customer-facing platform quote excludes the add-on; the six-month rate and written seat-based offer are not finalized.

The $124,000 is the platform; the add-on is separate

Ravi Avonbourne, internal Senior Account Executive

Two-week assistance and four-to-six-week implementation descriptions need explicit phase boundaries.

implementation for 88 seats is usually four to six weeks, most of it your side

Ravi Avonbourne, internal Senior Account Executive

Michael reported intermittent SAML-signature failures severe enough to defeat retries, with continued rejection in a clean staging session.

SSO login SAML logins fail with an invalid signature. It is intermittent rather than total, but it is enough to fail our retries.

Michael Clearwood (Celsara Partners end-user)

Support asserted a legacy-migration blocker and on-call escalation; the same escalation text appears after customer-confirmed recovery.

I have asked for this to be prioritised given it is blocking the migration off our legacy system. The on-call for feature-flags-proxy is aware.

Aisha Dalefield (support comment); later email attributed only to Support

Michael explicitly confirmed post-deployment SSO recovery and an unblocked nightly job.

Closing this from our side: SSO login has been fine since you deployed, and our nightly job is unblocked.

Michael Clearwood (Celsara Partners end-user)

Customer testimony is favorable for the existing payout-schedule deployment.

Jennifer, we have payout schedule in front of 118 users now with no complaints.

Linda Barncombe (External, Engineering Manager)

Usage growth and additional-team demand create an expansion lead, but capacity and tier implications need reconciliation.

Realistically, our usage is up roughly 117% on last quarter, which nobody expected.

Linda Barncombe (External, Engineering Manager)

Near-term signing interest is conditional on holding the quoted number, not an explicit renewal commitment.

If you can hold that number we can be done by the next exec sync.

Linda Barncombe (External, Engineering Manager)

The seller reports four tickets with a shared root cause and separately attributes evaluation log errors to v1.5.2.

Linda, four of your open tickets are the same root cause - I would like to close that first - if that is fair.

Joseph Alderwell (Internal, Senior Support Engineer); separate release attribution by Jennifer Clayhall

The seller quotes $162,000 for the platform, excluding the add-on and advising against buying it in year one.

the $162,000 is the platform; the add-on is separate and I would not buy it in year one.

Jennifer Clayhall (Internal, Enterprise Account Executive)

Net-revenue-retention measurement is a proposed customer outcome, with a seller-admitted reporting limitation.

And - where I would push back on us: reporting on net revenue retention is thinner than Okta's.

Jennifer Clayhall (Internal, Enterprise Account Executive)

Training and operating handoff requirements remain to be specified.

Who at Evidentis Credit Union has to be trained before the finance systems team can run it themselves?

Linda Barncombe (External, Engineering Manager)

Customers report established mobile-app use and positive feedback, not merely a planned pilot outcome.

To be fair, we have mobile app in front of 144 users now with no complaints.

Linda Barncombe (External, Engineering Manager)

Customer term preference and sign-off readiness are positive; the seller's hypothetical term objection is not a customer refusal.

We would rather sign for 36 months and lock the rate, as far as I know.

Nancy Alderthorpe (External, Office Manager)

An executive sponsor's analytics add-on interest is a separate expansion lead.

The exec sponsor is already asking about the analytics add-on.

Linda Barncombe (External, Engineering Manager)

Historical reliability and release-detection questions coexist with positive product feedback.

your status page had ingest-worker degraded twice last quarter

Linda Barncombe (External, Engineering Manager)

The seller flags plan rate limits before enabling additional teams.

One thing to flag: the rate limit on your plan is what 144 users hit first - that is where we are, anyway.

Joseph Alderwell (Internal, Senior Support Engineer)

Customer remains in a competitive evaluation and requires a written comparison before deciding.

We are still comparing you and the tool their US team already uses internally.

Linda Barncombe, external Engineering Manager

Security, not price, is the explicit gate; customer also requires a working product demonstration and clarity on integration, support and residency.

Sorry, security review is the gate the platform team worries about, not the price.

Linda Barncombe, external Engineering Manager

Budget is approved only in principle; timing and signer remain uncertain, with no decision before evaluation ends and little urgency before Q4.

And - budget is approved in principle by the platform team, but the timing is not fixed - but you know your side better than I do.

Linda Barncombe, external Engineering Manager

Customer-reported usage growth and requests from additional teams provide an expansion lead, not verified incremental revenue.

To be honest, our usage is up roughly 41% on last quarter, which nobody expected.

Nancy Alderthorpe, external; supporting statements by Linda Barncombe, external

Customer feedback is favorable on admin-console readiness and the rollout experience.

No open questions from our side on admin console, honestly.

Nancy Alderthorpe, external; related feedback by Linda Barncombe, external

Procurement and holding the commercial number are the buyer's remaining approval conditions.

The blocker on our side is procurement, not the technology.

Linda Barncombe, external

The proposed growth-tier change needs reconciliation with the promise to hold current terms.

That growth puts you in the next tier, so let me get you the better rate, as far as I know.

Wei Irondale, internal; related peak-load statement by Linda Barncombe, external

Customer reported repeated export failures and a payout-stability dependency for SOC 2 evidence collection.

Retries against eu-west-1 fail the same way. Request req_d706d78eb1. We need payout schedule stable before our SOC 2 evidence run.

Patricia Cliffcombe, Evidentis Credit Union (customer)

Support identified a missing index as its diagnosis, without documenting deployment of a fix.

The trace for req_d706d78eb1 points at a missing index.

Joseph Alderwell, Tenovia Analytics Support

Customer confirmed a full clean day in staging and expressed appreciation for sustained support.

Clean for a full day on our staging tenant now. Thanks for staying on it rather than closing it early.

Patricia Cliffcombe, Evidentis Credit Union (customer)

Customer reported duplicate alert writes and failing exports blocking an executive business review.

Every failing call is against /v1/media-transcoder/exports out of us-west-2. Blocking the executive business review.

Linda Barncombe, Evidentis Credit Union (customer)

Customer said the failure was not confined to the disaster-recovery site.

Sent - the request ids are in the attachment, and it fails the same way outside the disaster-recovery site.

Linda Barncombe, Evidentis Credit Union (customer)

Linda reported three or four successful batch reruns without duplicate records.

That has fixed it - we have run the batch three or four times since and it has not duplicating records once.

Linda Barncombe, Evidentis Credit Union (customer)

Kofi's later private note still describes second-region timeouts and asks to close the escalation loop.

Evidentis Credit Union escalation keeps timing out since we added the second region. 14:01 was the last occurrence - can we close Evidentis Credit Union's loop?

Kofi Clearby, Tenovia Analytics Support

Customer reported recurring silent loss of ledger-export final pages and reproduced it from a clean disaster-recovery session.

Hi team - the ledger export silently drops the last page of results. We first saw it over the weekend and it has happened on every second attempt since.

Linda Barncombe, Evidentis Credit Union (customer)

Linda reported stable ledger exports since deployment and her entire support team unblocked on August 15.

Closing this from our side: ledger export has been fine since you deployed, and our whole support team is unblocked.

Linda Barncombe, Evidentis Credit Union (customer)

The August 17 support email still calls the seasonal traffic peak blocked after customer-confirmed recovery.

I have asked for this to be prioritised given it is blocking the seasonal traffic peak. The on-call for support-portal is aware.

Hana Bradmoor, Tenovia Analytics Support

Customer reported persistent SAML login failures and said nothing had changed locally.

SSO login: SAML logins fail with an invalid signature. Started around 08:14 our time and it is still happening.

Patricia Cliffcombe, Evidentis Credit Union IT Operations Lead

Support named v1.3.2 as both the failing version and the fix; its explanation concerned export timeouts in us-west-2 rather than the original SAML symptom.

v1.3.2 has the fix and is rolling out now.

Sofia Jones, Tenovia Analytics support agent

Customer confirmed operation had resumed and shared the explanation internally.

Working again, and thank you for the write-up on a cache stampede after a flag flip - I have passed it to the team who were asking.

Patricia Cliffcombe, Evidentis Credit Union IT Operations Lead

Customer reported empty dashboards and wanted fault ownership clarified to avoid unnecessary integration debugging.

Dashboards render empty here since 08:01 with the reporting dashboard, and we would rather not spend the afternoon debugging our own integration if it is yours.

Mary Andersson, Rainshadow Technologies customer

Support said the issue remained with Tenovia and blocked the seasonal peak despite an announced rollout.

This is still with us. The internal bug names a migration that locked a hot table, and it is prioritised because it blocks the seasonal traffic peak.

Jennifer Ashbourne, Tenovia Analytics support

Support privately claimed a workaround before customer onboarding, with timing still requiring customer confirmation.

Rainshadow Technologies owner check has a workaround in place before customer onboarding. Rainshadow Technologies can confirm the timing

Jennifer Ashbourne, Tenovia Analytics support

Initial sizing and start-date language suggest prospective evaluation rather than a demonstrated renewal-rescue event.

Between us, we are sizing this at about 10 seats to begin with, give or take.

Daniel Bellshaw, external Systems Administrator

Security and regulatory residency are explicit qualification gates, with a CFO comparison required.

Security review is the gate their CFO worries about, not the price, subject to the usual caveats.

Daniel Bellshaw, external Systems Administrator

The seller offers a weekend batch import for 89.5 million records and claims tier headroom for hypothetical 103% growth; neither is a demonstrated outcome.

89.5 million records import in a weekend if we run it in batches rather than live.

Wei Alderton, internal Enterprise Account Executive

The seller attributes an evaluation timeout-related error to a release, while the engineer describes retry behavior rather than proven remediation.

DeadlineExceeded in your logs came from.

Wei Alderton, internal Enterprise Account Executive; behavior assurance from Wei Bainwell, internal Platform Engineer

The engineer tentatively attributes forecast-accuracy issues to schema rather than volume.

Your forecast accuracy numbers look like a schema problem rather than a volume one, honestly.

Wei Bainwell, internal Platform Engineer

Customer remains in competitive evaluation, with a board-review gate rather than a confirmed renewal decision.

We are still comparing you and the incumbent internally.

Daniel Bellshaw, External, Systems Administrator

Integration and support SLA are customer-stated evaluation concerns; seller assurances are not customer-validated resolution.

Yep, mostly the transaction dispute form integration story and the support SLA - that is where we are, anyway.

Daniel Bellshaw, External, Systems Administrator

Seller attributes evaluation log errors to v1.2.3, without demonstrating root-cause verification or recovery.

We shipped v1.2.3 the week you were evaluating, which is where the std::io::Error in your logs came from.

Wei Irondale, Internal, Account Executive

Customer requires 24 months, but seller term-rate descriptions need reconciliation.

Sorry, we would need a 24 month term rather than an annual one.

Daniel Bellshaw, External, Systems Administrator

The customer-raised $20,500 amount has unresolved renewal versus add-on scope.

is the $20,500 number the renewal or the renewal plus the add-on

Daniel Bellshaw, External, Systems Administrator

The platform team reportedly received no maintenance notice before the window began.

Sorry, nobody told the platform team about the last maintenance window until it had started.

Barbara Avonbury (Platform Engineer, external)

Sarah accepts responsibility to chase the issue and provide a plan, but resolution is not evidenced.

Going back a step, that is on me - I will chase it and get it to you with the plan - does that work for you?

Sarah Klausquist (VP Sales, internal)

The customer reports positive daily adoption and favorable platform-team feedback.

We have card authorisation webhook in front of 3,326 users now with no complaints.

Barbara Avonbury, external Platform Engineer

The customer proposes deferring an unspecified issue until renewal in 18 months, alongside conditional signing intent.

We can raise that at renewal in 18 months rather than now

Barbara Avonbury, external Platform Engineer

The customer expresses analytics expansion interest, but the seller explicitly defers scoping until after signature.

The - the exec sponsor is already asking about the analytics add-on - if that is fair.

Barbara Avonbury, external Platform Engineer

Growth-related capacity and tier pricing need a consistent written explanation, not an assumption of experienced capacity failure.

that growth puts you in the next tier, so let me get you the better rate.

Wei Alderton, internal Enterprise Account Executive

A seller-disclosed reporting limitation and the customer's source-of-truth requirement remain relevant fit checks despite positive product feedback.

reporting on p95 latency is thinner than Databricks's.

Wei Alderton, internal Enterprise Account Executive

Sponsor interest in an APAC team is a possible scope-discovery lead, with the organization and intent unresolved.

The exec sponsor is already asking about their APAC team.

Barbara Avonbury, External

The external participant requests availability-definition evidence rather than reporting experienced downtime.

you publish 99.56 percent - is that the whole platform or per service

Barbara Avonbury, External

James reported that escaped delimiters made the nightly-job export unparseable and tentatively associated the symptoms with v1.4.0.

It looks like it started with the v1.4.0 release; the SAML metadata endpoint escapes the delimiters so the file cannot be parsed for our nightly job.

James Martin, Spruceglen end-user

The only customer-substantiated commercial signal is lack of urgency before Q1.

Yep, there is no burning platform here before Q1, which is honestly the problem.

Patricia Hawkshaw, external Data Engineer

Customer is evaluating the vendor against an in-house build, suggesting acquisition qualification rather than established retention.

And - we are still comparing you and an in-house build internally.

Patricia Hawkshaw (external)

Customer requests identification of the services handling sanctions-screening traffic.

Which of your services would our sanctions screening traffic actually land on?

Patricia Hawkshaw (external)

External participant reports interest from two teams that were not in the pilot.

two teams that were not in the pilot have asked their head of support to add them.

Patricia Hawkshaw, Data Engineer, External

Own-account versus hosted-only deployment remains an unresolved qualification question in the supplied exchange.

can we run this in our own account or is it hosted only?

Patricia Hawkshaw, Data Engineer, External

Customer reports 434 KYC users without complaints, no open feature questions and an easier rollout than the prior migration.

We have KYC check in front of 434 users now with no complaints.

John Armitdale, external Support Manager

Two additional teams and executive interest in a second workspace support a distinct expansion lead.

On our side, two teams that were not in the pilot have asked their VP Engineering to add them.

John Armitdale, external Support Manager; second-workspace interest reported by Jessica Tarasenko, external Procurement Manager

Seller growth-tier guidance remains unreconciled against customer-reported 115% usage growth.

That growth puts you in the next tier, so let me get you the better rate.

Wei Alderton, internal Enterprise Account Executive; growth reported by John Armitdale, external Support Manager

The $142,500 figure appears in an unanswered customer question about renewal versus bundled add-on scope.

Wei, is the $142,500 number the renewal or the renewal plus the add-on?

John Armitdale, external Support Manager

Customer references a future renewal in 12 months, while Q4 describes a board/start discussion rather than a verified renewal deadline.

We can raise that at renewal in 12 months rather than now, more or less.

Jessica Tarasenko, external Procurement Manager

The customer reports substantial usage growth alongside positive invoice PDF adoption.

To be fair, our usage is up roughly 95% on last quarter, which nobody expected.

Elizabeth Greyhall, external Support Manager

A customer asks what changed after two prior billing-service degradations.

Your status page had billing-service degraded twice last quarter - what changed after that?

Noor Alderstead, external Engineering Manager

The seller connects an evaluation-log error to a release without establishing a completed fix.

So - right, we shipped v1.0.1 the week you were evaluating, which is where the *fs.PathError in your logs came from.

Michael Ashridge, internal Senior Software Engineer

The buyer explicitly frames $61,500 as a renewal-scope question; the seller identifies the amount as platform-only.

Is the $61,500 number the renewal or the renewal plus the add-on?

Noor Alderstead, external Engineering Manager

Closing intent is conditional on holding the price and reaching an unspecified go-live, not a completed renewal.

If you can hold that number we can be done by their go-live.

Elizabeth Greyhall, external Support Manager

The customer remains in a competitive evaluation and requires working KYC proof before commitment.

We are still comparing you and the other vendor on the shortlist internally.

Noor Alderstead, external Engineering Manager

Security, not price, is the customer's stated approval gate.

Security review is the gate their head of support worries about, not the price, subject to the usual caveats.

Noor Alderstead, external Engineering Manager

No decision is expected before the steering meeting; Q1 timing is not confirmed.

The evaluation runs until the steering meeting, so there is no decision before that - we can revisit that.

Noor Alderstead, external Engineering Manager

Source-of-truth behavior and integration/support ownership remain customer requirements needing written clarification.

We do not want a second source of truth.

Noor Alderstead, external Engineering Manager

The customer raises two historical export-service degradations without receiving demonstrated remediation.

your status page had export-service degraded twice last quarter - what changed after that?

Noor Alderstead, external Engineering Manager

The seller acknowledges weaker gross-margin reporting; the proposed schema explanation is not a verified business outcome.

reporting on gross margin is thinner than ServiceNow's

Ravi Avonbourne, internal Senior Account Executive

The seller quotes $204,000 for the platform, excluding the add-on; term economics remain prospective.

The $204,000 is the platform; the add-on is separate and I would not buy it in year one - I can check the exact figure.

Ravi Avonbourne, internal Senior Account Executive

Budget support is provisional, while the buyer continues comparing an existing internal alternative.

Budget is approved in principle by their head of support, but the timing is not fixed.

Joseph Eastford, external VP Operations

Customer explicitly identifies security, not price, as the gate.

Security review is the gate their head of support worries about, not the price.

Lisa Torson, external Data Engineer

Buyer rules out a decision before fiscal year end.

The evaluation runs until the end of the fiscal year, so there is no decision before that.

Lisa Torson, external Data Engineer

Working saved views and a written comparison remain precommitment requirements; seller admits weaker reopen-rate reporting.

And - our platform team will want to see saved views working before we commit.

Joseph Eastford, external VP Operations; reporting limitation and baseline promise from Ravi Avonbourne, internal Senior Account Executive

Connector escalation and operational handover require clarification, rather than evidencing an existing service incident.

Is the PagerDuty connector yours or a partner's, and who do we call at 2am?

Lisa Torson, external Data Engineer; related acceptance questions from Patricia Jones, external VP Engineering

Elizabeth is qualifying smaller-plan functionality and deployment in the buyer's own account.

To be fair, can we run this in our own account or is it hosted only, subject to the usual caveats.

Elizabeth Chadwood, External, CTO

Robert makes go-live conditional on weekly participation by the buyer's data owner.

Realistically, the go-live date holds if we have your data owner in the room each week - that is where we are, anyway.

Robert Brentwell, Internal, Support Engineer

Elizabeth offers to bring the Redshift documentation to the enablement group that week.

Send the Redshift doc and I will put it in front of the enablement group this week - does that work for you?

Elizabeth Chadwood, External, CTO

Customer reported API failures and an actual downstream-job pause for finance users.

We have paused the downstream job until we hear back.

David Avonworth, Caper Transport end-user; email signature: Procurement Manager

Support acknowledged investigation only; no remediation or restart result is supplied.

We are looking at is there an incident? the API is returning 503s on the disaster-recovery site now and will come back to you.

Freya Alderby, Tenovia Analytics Support, as identified in the email

The customer reported seasonal-peak blockage from two-factor session loss after a version bump.

We have not changed anything since the version bump. This is blocking the seasonal traffic peak.

Ravi Soles, Engineering Manager, Mizzle International

Support attributed the issue to a bad cache key and asserted that a v1.0.3 fix was rolling out.

v1.0.3 has the fix and is rolling out now.

Robert Bainton, Support, Tenovia Analytics

The final support update described an available workaround but a permanent fix still in review.

We have a workaround for two-factor enrolment in the meantime; the permanent fix is in review.

Robert Bainton, Support, Tenovia Analytics

An external participant reports withheld renewal approval, contradicting the seller's signature-ready framing.

To be clear, their COO has not approved the renewal as it stands.

Richard Ashcombe, external Systems Administrator

William promises ownership of two escalations, but their subject and completion are unknown.

Right, so - I am escalating all Two of them today and will own the follow-up.

William Alderfield, internal Sales Manager

Richard reports 200 users with no complaints, ahead-of-expectation adoption and positive daily feedback.

We have payout schedule in front of 200 users now with no complaints - assuming nothing changes.

Richard Ashcombe, external Systems Administrator

Two non-pilot teams have requested access and the executive sponsor is interested in a second workspace.

Well, two teams that were not in the pilot have asked their head of support to add them.

Richard Ashcombe, external Systems Administrator

Richard prefers a six-month rate-locked agreement and indicates a conditional close by board review.

We would rather sign for 6 months and lock the rate.

Richard Ashcombe, external Systems Administrator

The seller flags a 200-user rate-limit boundary and a tier change with growth, without evidence of current customer throttling.

To be fair, one thing to flag: the rate limit on your plan is what 200 users hit first.

Wei Alderton, internal Enterprise Account Executive

Wei links an evaluation error to a release, but the fragmented transcript supplies no verified remediation.

We shipped v1. 2. 0 the week you were evaluating, which is where the runtime.

Wei Alderton, internal Enterprise Account Executive

Fawn's Head of IT reported that finance users could not complete KYC in us-east-1.

everyone in the finance group reports that the KYC check stalls at ninety per cent and then restarts in us-east-1.

Patricia Lucucci, Head of IT, Fawn Manufacturing

Customer directly connected the incident to a blocked board reporting pack.

This is blocking the board reporting pack.

Patricia Lucucci, Head of IT, Fawn Manufacturing

The customer identified session logouts across workspaces as a partner-handover evaluation blocker.

We are evaluating admin console for the integration handover to our partner and hit a blocker: it logs the user out mid-session. Tried on our second workspace with the same result (ref req_0cd0625fec).

Patricia Jones, Holly Partners (customer)

Support asserted that an orphaned-lock fix had shipped and expected console behaviour to recover.

The fix for an orphaned lock left by a cancelled job went out this morning. Admin console should be behaving again on our second workspace.

Mary Barnwood, Tenovia Analytics Support (agent)

The later support update reported no change and identified the platform team as the escalation destination.

No change yet - req_0cd0625fec is with the platform team and I am chasing it daily.

Mary Barnwood, Tenovia Analytics Support (agent)

Omar reported dispute-form records belonging to another workspace, affecting Coda's two busiest workspaces.

the transaction dispute form returns records belonging to a different workspace. our two busiest workspaces are affected.

Omar Ashwood, Coda Financial customer

The customer expressed prolonged repair frustration and conditional intent to build a workaround, not refusal to renew.

Two weeks on this now. If a connection pool exhausted by a slow query is not going to be fixed soon, tell us and we will build around it.

Omar Ashwood, Coda Financial customer

Support reported a us-west-2 rollback and requested confirmation, without establishing restored dispute-form behavior.

Rolled back in us-west-2 - could you retry and confirm?

Robert Bainton, Tenovia Analytics Support

The customer reported long-payload truncation on its on-premise card-authorisation gateway, persisting after a clean-session test.

We tried from a clean session on our on-premise gateway and the card authorisation webhook still silently truncating.

Marta Fernmoor, Coda Financial customer

The customer explicitly limited immediate urgency and tied escalation to an annual pricing refresh.

Not urgent yet, but it becomes urgent at the annual pricing refresh.

Marta Fernmoor, Coda Financial customer

Support requested a failed-attempt request ID after previously acknowledging, attaching and diagnosing the existing ID.

I need one more thing from you: the request id from a failed attempt on our on-premise gateway.

Inge Anderson, Tenovia Analytics Support

Hana reported duplicate custom-field writes in APAC affecting Berlin analysts after an auditor key-rotation request.

Since our auditors asked us to rotate keys, custom fields duplicates every record it writes. It reproduces on the APAC region for the analysts in our Berlin office.

Hana Chen (Easton Partners customer; signed Support Manager)

The customer explicitly identified a next-week go-live blocker; the supplied support response only acknowledges investigation.

This is blocking our go-live next week.

Hana Chen (customer statement); Barbara Yorkcroft (support acknowledgement)

Customer reports stale payout data requiring a hard refresh and says the disaster-recovery integration issue blocks onboarding.

It reproduces on the disaster-recovery site for our API integration. Request id req_72d559f7ed is one example. This is blocking customer onboarding.

Patricia Mossbury, Head of IT, Jermyn Financial

Support attributes the issue to rate-limit configuration and claims disaster-recovery-site mitigation.

This is a rate-limit misconfiguration rather than anything on your side. We have mitigated it on the disaster-recovery site - could you retry?

Joseph Kenford, Support, Tenovia Analytics

Support subsequently reports no change and says the request remains with the platform team.

No change yet - req_72d559f7ed is with the platform team and I am chasing it daily.

Joseph Kenford, Support, Tenovia Analytics

Aisha identifies procurement as the blocker and security as the gate procurement cares about, not price.

The blocker on our side is procurement, not the technology.

Aisha Fontetti, external IT Operations Lead

The seller proposes integration review before a board review and a sandbox; neither completion nor customer acceptance is supplied.

I will ask our solutions engineer to look at your integration before the board review

Wei Alderton, internal Enterprise Account Executive

Joseph reported continuous webhook/export rounding differences after scaling; Jennifer subsequently reported reproducing the webhook issue in the EU region.

the webhook subscription rounds the totals differently from the export. We first saw it the moment we scaled up and it has happened continuously since then since.

Joseph Clearbury, Peverell International, customer; reproduction reported by Jennifer Ashbourne, Support

Joseph also reported allocation errors on the billing-invoices endpoint, a symptom not explicitly connected to the rounding discrepancy.

Another one just now, same std::alloc::AllocError against /v1/billing/invoices. Trace 768028963c323dbd if you want it.

Joseph Clearbury, Peverell International, customer

Jennifer stated that an expired-credential fix had shipped and expected webhook behavior to recover.

The fix for an expired credential went out this morning. Webhook subscription should be behaving again on the EU region.

Jennifer Ashbourne, Tenovia Analytics Support

An internal note identified an escalation ownership gap while characterizing the matter as nonurgent.

Peverell International escalation is waiting on an owner, not urgent for Peverell International

Jennifer Ashbourne, Tenovia Analytics Support

Robert reported recurring ReferenceError failures under load, unsuccessful retries and a need for stable KYC before go-live.

Retries against eu-west-1 fail the same way. Request req_b1f9789248. We need KYC check stable before our go-live next week.

Robert Alderhall, Peverell International, customer

The customer confirmed hourly load-related failures on the Canadian data residency tenant after support reported reproduction there.

Yes, same on the Canadian data residency tenant. It has happened about once an hour under load since Monday.

Robert Alderhall, Peverell International, customer; reproduction reported by John Ashwood, Support

John offered an interim workaround while saying the permanent fix remained in review.

We have a workaround for KYC check in the meantime; the permanent fix is in review.

John Ashwood, Tenovia Analytics Support

Robert described an ACH evaluation blocker, also reproduced in staging, rather than an established production outage or renewal decision.

We are evaluating ACH batch for the integration handover to our partner and hit a blocker: it truncates anything longer than a few thousand characters.

Robert Alderhall, Peverell International, customer

Hana attributed the trace to a deleted-group permission and provided a write-up, not a stated repair.

The trace for req_7d5f38b430 points at a permission inherited from a deleted group.

Hana Bradmoor, Tenovia Analytics Support

An internal note claimed a Salesforce-sync workaround and placed the next handoff with Peverell.

Salesforce sync for Peverell International has a workaround in place - Peverell International has the next handoff

Hana Bradmoor, Tenovia Analytics Support

Patricia linked invoice-PDF non-dispatch in us-east-1 to a blocked regulatory submission deadline.

This is blocking the regulator's submission deadline.

Patricia Bellford, Peverell International, customer

Robert acknowledged investigation, but the supplied ticket snapshot has no assignee and no demonstrated remediation.

We are looking at request: raise our invoice PDF rate limit before the regulator's submission deadline now and will come back to you.

Robert Deepcroft, Tenovia Analytics Support; assignee status from ticket metadata

Joseph reported a dozen overnight reconciliation discrepancies with error 409 and required stability for disaster-recovery certification.

It has happened a dozen times overnight, always with error 409. We need it stable before our disaster-recovery certification - what do you need from us?

Joseph Clearbury, Peverell International, customer

Hana acknowledged the title's TypeError/release framing, while the ticket snapshot remained unassigned.

We are looking at typeError on reconciliation report after the v1.5.0 release now and will come back to you.

Hana Bradmoor, Tenovia Analytics Support; assignee status from ticket metadata

Patricia reported duplicate KYC notifications affecting about a dozen users and subsequently confirmed production impact.

about a dozen users report that the KYC check sends the notification twice. Started over the weekend; no config changes on our side.

Patricia Bellford, Peverell International, customer

The customer sought a shareable update because the issue could shape the quarter's executive business review.

They are asking whether to plan the executive business review around this for the quarter.

Patricia Bellford, Peverell International, customer

Robert explicitly rejected the retry-storm cause, first in a comment and again in a later email.

An update I owe you rather than a fix: the change we thought caused this shipped after we enabled SSO, so a retry storm from their integration is not it after all.

Robert Brentwell, Tenovia Analytics Support

Robert also asserted that a retry-storm fix had shipped and expected production KYC to recover.

The fix for a retry storm from their integration went out this morning. KYC check should be behaving again on production.

Robert Brentwell, Tenovia Analytics Support

The customer is willing to defer an unspecified matter until renewal in six months.

We can raise that at renewal in 6 months rather than now ... if that makes sense.

Robert Alderhall, external Platform Engineer

The customer requests us-east-1 residency for recurring regulatory scrutiny.

To be honest, the thing is, jennifer, can you pin the data to us-east-1?

Robert Alderhall, external Platform Engineer

Mary reports that the renewal lacks head-of-support approval.

To be clear, their head of support has not approved the renewal as it stands.

Mary Alderfield, external Data Engineer

Elizabeth reports two reconciliation-report outages since Q2 began.

Reconciliation report has been down twice since Q2 started.

Elizabeth Avonbourne, external Systems Administrator

Another outage before the board review would undermine Mary's ability to defend the product.

If reconciliation report goes down again before the board review I cannot defend this.

Mary Alderfield, external Data Engineer

Mary reports paying for 1,418 seats while half have stopped logging in.

The thing is, we are paying for 1,418 seats and half of them have stopped logging in.

Mary Alderfield, external Data Engineer

Robert Gonzalez explicitly takes responsibility for an escalation, but completion is not shown.

I am escalating all Two of them today and will own the follow-up.

Robert Gonzalez, internal Account Executive

Mary remains engaged and agrees to involve the reported approval stakeholder.

Send it over and I will loop in their head of support - that is where we are, anyway.

Mary Alderfield, external Data Engineer

Ana reports that the referenced COO has not approved the renewal as presented.

To be clear, their COO has not approved the renewal as it stands.

Ana Rainham, external Head of Infrastructure

Ana reports that half of 4,586 paid seats have stopped logging in.

We are paying for 4,586 seats and half of them have stopped logging in.

Ana Rainham, external Head of Infrastructure

Diego reports six months of worsening support and an internally advocated in-house replacement.

Barbara, your support times have gone the wrong way for 6 months, and an in-house build is being pushed internally.

Diego Calderwick, external VP Engineering

The customer reports outage-related trust damage, while the seller offers narrower failover assurances and acknowledges a missed notice.

Honestly, the last outage cost us a lot of trust - I can check the exact figure.

Diego Calderwick, external VP Engineering

The customer sets an end-of-month delivery gate; Barbara promises recovery work without evidence of completion.

Send it before the end of the month or this stalls.

Diego Calderwick, external VP Engineering

Barbara describes $156,500 as platform-only, but the renewal allocation, billing period and executed amount remain unverified.

Yep, the $156,500 is the platform; the add-on is separate and I would not buy it in year one - I can check the exact figure.

Barbara Barnton, internal Business Development Representative

Customer explicitly identifies security review, not price, as the gate.

Security review is the gate the security team worries about, not the price.

Diego Calderwick (External, VP Engineering)

Customer asks whether $159,000 is renewal-only or includes the add-on; the scope is unanswered.

Is the $159,000 number the renewal or the renewal plus the add-on?

Diego Calderwick (External, VP Engineering); seat/tier statement from Richard Marley (Internal, Sales Manager)

Procurement requires a written comparison while the buyer considers a spreadsheet-and-cron alternative.

Procurement wants a written comparison before we decide.

Diego Calderwick, external VP Engineering

Working payout schedule is an explicit commitment gate, not an achieved pilot outcome.

Right, our platform team will want to see payout schedule working before we commit - if that is fair.

Diego Calderwick, external VP Engineering

The buyer asks who will own migration; the supplied discussion does not identify that project owner.

To be honest, michael, who owns the migration on your side once we sign?

Diego Calderwick, external VP Engineering

The seller gives unreconciled pricing explanations for the requested 36-month term.

Honestly, for what it is worth, a 36 month term is possible, at a different rate - I will show you.

Michael Dalethorpe, internal Software Engineer

Q4 onboarding is discussed, but the decision/start schedule remains relative and uncommitted.

How does onboarding look if we start in Q4?

Diego Calderwick, external VP Engineering

The customer explicitly says procurement has not approved the renewal as it stands.

To be clear, procurement has not approved the renewal as it stands, subject to the usual caveats.

Barbara Thompson, external Data Engineer

Reported repeated outages have created a conditional renewal-defense threshold before quarter end.

if attachment upload goes down again before quarter end I cannot defend this.

Barbara Thompson, external Data Engineer; repeated outages also reported by Mateo Hernandez, external Product Manager

The customer reports deteriorating support and active internal consideration of the US team's alternative tool.

your support times have gone the wrong way for 12 months, and the tool their US team already uses is being pushed internally.

Mateo Hernandez, external Product Manager

The customer reports paying for 506 seats while half have stopped logging in.

We are paying for 506 seats and half of them have stopped logging in - assuming nothing changes.

Barbara Thompson, external Data Engineer

$148,000 is an unresolved customer question about renewal versus renewal-plus-add-on value.

Yep, is the $148,000 number the renewal or the renewal plus the add-on?

Elizabeth Ashford, external Engineering Manager

William promises RCA/remediation milestones, while Kofi proposes common-root-cause work and named coverage; completion is not shown.

I will have the attachment upload RCA with you before quarter end - we can revisit that.

William Alderfield, internal Sales Manager; related proposals by Kofi Clearby, internal Support Operations Analyst

Customer reports renewal approval withheld while procurement has already discussed another vendor.

To be clear, procurement has not approved the renewal as it stands.

Barbara Hernandez, Support Manager, External

Customer reports two attachment-upload outages since Q3 began, with a seller-acknowledged maintenance-notice gap.

Attachment upload has been down twice since Q3 started.

Barbara Hernandez, Support Manager, External

Customer says the attachment-upload RCA was never received; delivery and escalation remain promises.

We also never got the RCA for the attachment upload failures

Barbara Hernandez, Support Manager, External

Customer sets a fiscal-year-end delivery condition that could stall the discussion; the exact deliverable is unclear.

Send it before the end of the fiscal year or this stalls

Tomas Avonby, Platform Engineer, External

Seller quotes $150,500 for the platform separately from the add-on, without a verified billing basis.

The $150,500 is the platform; the add-on is separate and I would not buy it in year one, more or less.

Wei Alderton, Enterprise Account Executive, Internal

Seller attributes evaluation FetchError logs to v1.5.2, without proving that the upload failures were repaired.

We shipped v1.5.2 the week you were evaluating, which is where the FetchError in your logs came from.

Wei Alderton, Enterprise Account Executive, Internal

Customer says another admin-console outage would make the purchase indefensible after repeated outages and lost trust.

If admin console goes down again before the end of the month I cannot defend this.

Barbara Hernandez (External, Support Manager)

Customer makes timely RCA delivery a condition for avoiding a stalled transaction.

Yeah - send it before the end of the month or this stalls - we can revisit that.

Tomas Avonby (External, Platform Engineer)

Seller acknowledges a missed maintenance notice; concrete corrective changes are not documented.

I mean, you should have had the maintenance notice; I will find out why you did not.

Wei Alderton (Internal, Enterprise Account Executive)

Seller quotes $124,500 platform-only and describes a 36-month option without a per-seat price advantage.

And - honestly, the $124,500 is the platform; the add-on is separate and I would not buy it in year one.

Wei Alderton (Internal, Enterprise Account Executive)

Seller raises a possible seat-utilization issue, but customer underuse is not established.

The 64 seats and the quiet ones are worth a conversation - not at renewal, now, roughly.

Wei Alderton (Internal, Enterprise Account Executive)

Omar reported dispute-form records belonging to another workspace, affecting Coda's two busiest workspaces.

the transaction dispute form returns records belonging to a different workspace. our two busiest workspaces are affected.

Omar Ashwood, Coda Financial customer

The customer expressed prolonged repair frustration and conditional intent to build a workaround, not refusal to renew.

Two weeks on this now. If a connection pool exhausted by a slow query is not going to be fixed soon, tell us and we will build around it.

Omar Ashwood, Coda Financial customer

Support reported a us-west-2 rollback and requested confirmation, without establishing restored dispute-form behavior.

Rolled back in us-west-2 - could you retry and confirm?

Robert Bainton, Tenovia Analytics Support

The customer reported long-payload truncation on its on-premise card-authorisation gateway, persisting after a clean-session test.

We tried from a clean session on our on-premise gateway and the card authorisation webhook still silently truncating.

Marta Fernmoor, Coda Financial customer

The customer explicitly limited immediate urgency and tied escalation to an annual pricing refresh.

Not urgent yet, but it becomes urgent at the annual pricing refresh.

Marta Fernmoor, Coda Financial customer

Support requested a failed-attempt request ID after previously acknowledging, attaching and diagnosing the existing ID.

I need one more thing from you: the request id from a failed attempt on our on-premise gateway.

Inge Anderson, Tenovia Analytics Support

Hana reported duplicate custom-field writes in APAC affecting Berlin analysts after an auditor key-rotation request.

Since our auditors asked us to rotate keys, custom fields duplicates every record it writes. It reproduces on the APAC region for the analysts in our Berlin office.

Hana Chen (Easton Partners customer; signed Support Manager)

The customer explicitly identified a next-week go-live blocker; the supplied support response only acknowledges investigation.

This is blocking our go-live next week.

Hana Chen (customer statement); Barbara Yorkcroft (support acknowledgement)

Customer reports stale payout data requiring a hard refresh and says the disaster-recovery integration issue blocks onboarding.

It reproduces on the disaster-recovery site for our API integration. Request id req_72d559f7ed is one example. This is blocking customer onboarding.

Patricia Mossbury, Head of IT, Jermyn Financial

Support attributes the issue to rate-limit configuration and claims disaster-recovery-site mitigation.

This is a rate-limit misconfiguration rather than anything on your side. We have mitigated it on the disaster-recovery site - could you retry?

Joseph Kenford, Support, Tenovia Analytics

Support subsequently reports no change and says the request remains with the platform team.

No change yet - req_72d559f7ed is with the platform team and I am chasing it daily.

Joseph Kenford, Support, Tenovia Analytics

James reported that escaped delimiters made the nightly-job export unparseable and tentatively associated the symptoms with v1.4.0.

It looks like it started with the v1.4.0 release; the SAML metadata endpoint escapes the delimiters so the file cannot be parsed for our nightly job.

James Martin, Spruceglen end-user

Patricia linked invoice-PDF non-dispatch in us-east-1 to a blocked regulatory submission deadline.

This is blocking the regulator's submission deadline.

Patricia Bellford, Peverell International, customer

Robert acknowledged investigation, but the supplied ticket snapshot has no assignee and no demonstrated remediation.

We are looking at request: raise our invoice PDF rate limit before the regulator's submission deadline now and will come back to you.

Robert Deepcroft, Tenovia Analytics Support; assignee status from ticket metadata

Joseph reported a dozen overnight reconciliation discrepancies with error 409 and required stability for disaster-recovery certification.

It has happened a dozen times overnight, always with error 409. We need it stable before our disaster-recovery certification - what do you need from us?

Joseph Clearbury, Peverell International, customer

Hana acknowledged the title's TypeError/release framing, while the ticket snapshot remained unassigned.

We are looking at typeError on reconciliation report after the v1.5.0 release now and will come back to you.

Hana Bradmoor, Tenovia Analytics Support; assignee status from ticket metadata

Joseph reported continuous webhook/export rounding differences after scaling; Jennifer subsequently reported reproducing the webhook issue in the EU region.

the webhook subscription rounds the totals differently from the export. We first saw it the moment we scaled up and it has happened continuously since then since.

Joseph Clearbury, Peverell International, customer; reproduction reported by Jennifer Ashbourne, Support

Joseph also reported allocation errors on the billing-invoices endpoint, a symptom not explicitly connected to the rounding discrepancy.

Another one just now, same std::alloc::AllocError against /v1/billing/invoices. Trace 768028963c323dbd if you want it.

Joseph Clearbury, Peverell International, customer

Jennifer stated that an expired-credential fix had shipped and expected webhook behavior to recover.

The fix for an expired credential went out this morning. Webhook subscription should be behaving again on the EU region.

Jennifer Ashbourne, Tenovia Analytics Support

An internal note identified an escalation ownership gap while characterizing the matter as nonurgent.

Peverell International escalation is waiting on an owner, not urgent for Peverell International

Jennifer Ashbourne, Tenovia Analytics Support

Duplicate production notifications created a go-live readiness concern, although the customer explicitly said it was not yet urgent.

Could you check retention policy? It sends the notification twice - error 502, request req_ae3aab1b4e, on production. Not urgent yet, but it becomes urgent at our go-live next week.

Anthony Antonenko, Cautera Technologies Platform Engineer; customer

Richard reported stale production payout configuration with a payroll-cutover dependency.

It applies yesterday's configuration instead of the current one - error 422, request req_1f70e5b27b, on production. Not urgent yet, but it becomes urgent at payroll cutover.

Richard Alderwell, Cautera Technologies end-user

John acknowledged investigation, without a supplied recovery result.

We are looking at payout schedule reading stale configuration on production now and will come back to you.

John Ashwood, Tenovia support

The customer reported SSO login failures affecting everyone using SSO and paused a downstream job pending a response.

for everyone who logs in via SSO: SSO login SAML logins fail with an invalid signature, first noticed at 14:59. We have paused the downstream job until we hear back.

Jennifer Ashford, Security Engineer, Cautera Technologies

Support acknowledged investigation despite new/unassigned ticket metadata, but supplied no diagnosis or recovery result.

We are looking at is there an incident? SAML logins fail with an invalid signature on the Canadian data residency tenant now and will come back to you.

Robert Deepcroft, Tenovia Analytics Support

Jessica reported unparsable sanctions-screening exports in the sandbox, with three or four occurrences and error 503.

Reporting this from our sandbox at 16:42: sanctions screening escapes the delimiters so the file cannot be parsed.

Jessica Ashford, Obsidian Partners, Systems Administrator

The customer made stability a requirement before an annual pricing refresh, creating a commercial qualification lead rather than a proven renewal rescue.

We need it stable before the annual pricing refresh - what do you need from us?

Jessica Ashford, Obsidian Partners

Inge acknowledged investigation, but supplied text contains no remediation or customer retest.

We are looking at sanctions screening producing an unparsable export for our warehouse scanners now and will come back to you.

Inge Anderson, Tenovia Support