Repository navigation
trunk-merge/pr-119223/232f83c1-5d1e-4bf0-8adc-8e3736e63f44 - #123590
Closed
trunk-io[bot] wants to merge 310 commits into
Closed
trunk-io[bot] wants to merge 310 commits into
trunk-io[bot] wants to merge 310 commits into
Conversation
Generated-By: PostHog Desktop Task-Id: fce9f1ec-a08a-41ee-ae3b-2ec268596156
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
A team whose query slots stay full past the limiter's retry budget got a 429 with no wait hint, so API clients and the MCP server retried blind. Every concurrency 429 now carries Retry-After and names the wait in its message.
10 updated Run: e2c0db41-90d7-468a-bb48-ee365e1f4f2a Co-authored-by: Radu-Raicea <15457029+Radu-Raicea@users.noreply.github.com>
Marketing analytics conversion recordings, data catalog metric runs and endpoint runs raised the same 429 without a wait, so clients on those paths still retried blind. Each site's 429 test now asserts the header.
The support-reply coordinator dropped ineligible tickets without a trace,
so a ticket the team started (for example one created through the compose
API) looked identical to one still waiting for its AI draft.
For teams that pass every team-level gate, the coordinator now writes
ai_triage {status: done, result: skipped_team_replied |
skipped_channel_excluded} into tickets whose ai_triage is still empty, in
one bulk update per result per tick. The channel gate moves below the AI
data approval and knowledge readiness gates so the channel reason is only
recorded on teams that would otherwise draft. The global dispatch cap now
skips instead of breaking out of the loop, so team-replied tickets past
the cap are still recorded.
Rejected: recording team-level reasons (flag off, approval missing) | those are settings, not per-ticket facts
Rejected: backfilling existing tickets | out of scope, only new tickets in the lookback get a reason
Confidence: high
Scope-risk: narrow
Ticket: ai-triage-skip-visibility/U1
Tickets the AI support agent skipped now carry a result, so the panel tag, list column, and AI triage filter need labels for skipped_team_replied and skipped_channel_excluded. The empty-state copy said "AI has not processed this ticket yet", which read as pending even for tickets the agent will never draft; it now explains when the agent drafts and that it skips tickets the team already replied to. Generated OpenAPI clients and MCP tool-schema snapshots are regenerated from the new AI_TRIAGE_FILTER_VALUES. The desktop api-client is left for CI to regenerate. Confidence: high Scope-risk: narrow Not-tested: desktop api-client regeneration (generator not installed locally) Ticket: ai-triage-skip-visibility/U2
The two-sentence explanation was long for a collapsed side panel. The new copy keeps the one rule support teams hit most: AI skips tickets the team already replied to. Confidence: high Scope-risk: narrow
A first-draft ticket counts as engaged when it has any non-customer comment, including private AI notes such as the signals report writeback. Labeling those tickets "Skipped, team replied" claimed the team answered when nobody did. The label now needs a comment that is neither customer nor AI; the skip itself is unchanged. Confidence: high Scope-risk: narrow
…into john/ai-triage-skip-visibility
8 updated Run: 94b4da69-eff3-44a7-8c75-2f7ba9d2376d Co-authored-by: Radu-Raicea <15457029+Radu-Raicea@users.noreply.github.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Generated-By: PostHog Desktop Task-Id: 3c795feb-ff55-4f59-b65a-a28d95757261
Add the slack-app-interview-recruitment flag. Its variant is the campaign and its payload holds the message and the booking link. The Home tab shows a "Book a chat" button, and the bad-rating modal adds one under the reason field at most once in 30 days. The link carries the campaign, surface and invitation id as cal.com metadata, and clicks are captured. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Generated-By: PostHog Desktop Task-Id: 3f610b01-67f3-4926-a0dc-4d623f01e77c
…g as an error Bing Webmaster Tools returns an "ERROR!!! ThrottleIP" fault when the caller's egress address hits its rate limit, the sibling of the already-handled "ERROR!!! ThrottleUser" fault. Only ThrottleUser was listed in get_retryable_errors(), so a ThrottleIP fault fell through unclassified and was reported to error tracking on every attempt instead of retrying quietly. Add "ERROR!!! ThrottleIP" to BingWebmasterToolsSource.get_retryable_errors(), alongside the existing ThrottleUser entry. The activity already retries unmatched errors via Temporal's default policy; this only stops it from being logged as an exception on each attempt. Generated-By: PostHog Desktop Task-Id: 6f4864cc-5cd8-4c61-8612-6d50c551572c
Contributor
🤖 CI report
|
Author
|
trunk-io
Bot
deleted the
trunk-merge/pr-119223/232f83c1-5d1e-4bf0-8adc-8e3736e63f44
branch
October 26, 2026 18:33
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request was created and is being managed by Trunk Merge.
This pull request is based on the master branch at SHA 22e6bddb84b22be24dd2631a9bbb6b1fe5edcc8e.
See more details here.
When CI completes, this pull request will be closed automatically.
Pull Requests Being Tested
This pull request is testing the changes from pull request 119223.
Dependencies
This pull request depends on the changes from pull requests 122674, 123578, 122787, 123356, 121616, and 123393.