Answer
What is broken or missing for partners right now, dated by the note or code it comes from, with the workaround we give until the fix lands.
Today
Newest first. The date is the date of the source. An issue fixed since its note is not listed.
Found in the code on 26 Oct
| Issue | Workaround | Source |
|---|---|---|
| On production there is no button for our team to move a sent brief on. The buttons are on brew origin/main and going to staging now; production gets them with the next promote. | Until then an engineer calls the status route on production. The partner sees Sent until then. | brew/public/brief-staff.js:1-16; brew/jam-brief.js:406-416; deploy state 26 Oct |
| The in app deletion sheet promises deletion within 7 days. The privacy page gives no time. | Answer every deletion request within 7 days, which keeps both true. | brew/public/live.js:349; brew/legal-pages.js:34 |
Production has no deletion job yet. db/delete-brand.mjs is on origin/main, but production needs the next promote for its data_deletions table and a brew-prod-ops job made once. |
On staging run the brew-ops job. On production wait for the promote, or an engineer deletes by hand. See data requests. |
brew/db/delete-brand.mjs:1-10; brew/docs/production.md:95-106 |
| Emails still name the product in the sender, the header and the footer. On origin/main the name comes from one constant, still Brew, and the ShopOS team is gone from every email. Production still sends the old wording until the next promote. | None yet. The rename is one line once the name is picked. | brew/auth.js:177; brew/build.js:1031; brew/mail-layout.js:55, 68; brew/product-name.js:1-6 |
| Emails on production still say moves, such as the weekly digest and the open your feed reminder. Fixed on origin/main: they say plays. | None needed after the next promote. | brew/digest.js:137; brew/confirm-remind.js:84; brew/build.js:1013 |
| Finals on production are made by our own image path, because Sloosh stays off production by Param's choice. | None needed. Finals say made by Brew. | brew commit 0fc7cfc |
From the jam RCA, 26 Oct
| Issue | Workaround | Source |
|---|---|---|
| The first look is still in the panel, not on the stage. | Open the panel to see it. | memory brew-jam-rca-2026-10-26 |
| Review quotes in drafts are not yet attributed. | Check a quote against the reviews before using it. | memory brew-jam-rca-2026-10-26 |
| The product is still named Brew in the interface. Since 26 Oct on origin/main the name is one constant, and about 880 customer strings say we or our team instead. A few still name it, such as the mail sender and the Slack app. | None yet. | memory brew-jam-rca-2026-10-26; brew/product-name.js:1-6; brew/auth.js:177; brew/docs/slack-app-manifest.json:4, 10; brew commit ca2bc7b |
From QA round 2, re-checked on production on 25 Oct night
| Issue | Workaround | Source |
|---|---|---|
| The first load after a release is slow. | Reload once. Later loads are fast. | memory brew-qa-round2-2026-10-24 |
| Some cards speak in a we and our voice. | Treat it as wording only. The facts on the card stand. | memory brew-qa-round2-2026-10-24 |
| Arata's MitoActive has no Shopify 30 day units, possibly because it is on preorder. | Read its sales from Shopify directly. | memory brew-qa-round2-2026-10-24 |
| Budget bars show only when a live Meta shift card exists. | None needed. By design until more cards carry budgets. | memory brew-qa-round2-2026-10-24 |
| Email and WhatsApp tools found on the site appear only after a re-read. | Ask us to re-read the store. | memory brew-qa-round2-2026-10-24 |
Platform and approvals, 21 to 25 Oct
| Issue | Workaround | Source |
|---|---|---|
| Meta App Review is not submitted. On 24 Oct business verification was still in review and two screencasts were missing. Only people with a role on our Meta app can connect Meta. | We add the partner's Meta person as a role on our app. | memory brew-meta-app-review, brew-real-connectors |
| Shopify public app submitted 21 Oct, not yet approved. One click Shopify install is off. | The partner connects with their own Dev Dashboard app, guided in the connect sheet. | memory brew-shopify-app-review, brew-real-connectors |
| The default compute service account has project wide secret and run admin rights. Param has not decided. | None needed for partners. | memory brew-prod-backend |
| Meta's privacy and data deletion URLs point at the staging address. | They still resolve. Update them before App Review. | memory brew-meta-app-review |
Older, still open
| Issue | Date | Source |
|---|---|---|
| Our team is named three ways across Plays. Customer strings were changed to our team on origin/main on 26 Oct; not re-checked across Plays since. | 20 Oct | memory brew-qa-audit-2026-10-20; brew commit ca2bc7b |
| Dead options code in the jam. Not visible to partners. | 20 Oct | memory brew-qa-audit-2026-10-20 |
| Sunk same ask followers are still served at the end of the feed. | 20 Oct | memory brew-qa-audit-2026-10-20 |
| Open by decision: Meta app mode, pricing and trial, email sign in, the ownership gate, a daily card limit, a cookie banner and the AI visibility focus. | 19 Oct | memory brew-qa-sweep-2026-10-19 |
Tomorrow
| Version | Tag | Item |
|---|---|---|
| v1 | New | This list is the single place partners' issues are tracked. Each row moves to the decisions log or out of the list when its fix is live. |
| v1 | Stays | Brief status buttons for our team inside the jam, built on origin/main; on production after the next promote. |
| v1 | Changes | Customer emails drop the product name from the sender, header and footer once the name is picked. Our company name and moves are gone on origin/main. |
| v1 | Changes | The production deletion job, built on origin/main, made on production after the next promote, so the 7 day promise does not rest on a manual edit. |
| v1 | New | A partner facing version of this list in the help centre, written plainly, with only the issues partners can see. |
How we do it
When a QA round, an audit or a partner reports a bug, add a row here with the date of the source and a workaround a partner can use today.
Fix it in code for every brand, add a test, heal saved data, then deploy. Never patch one brand's data alone.
When the fix is live on production, remove the row and tell any partner who reported it.
Before telling Param something is still broken, check
git log origin/mainfor a later fix:git -C /Users/param/Documents/ChatGPT/brew log origin/main --since=<date> --format='%h %cs %s'
Numbers
| Metric | Definition | Where measured | State |
|---|---|---|---|
| Open issues | Rows in this list | This document | Proposed |
| Age of the oldest row | Days since its source date | This document | Proposed |
| Partner visible issues | Rows a partner can see on a screen | This document | Proposed |
Open
- Should partners see a known issues page? Proposal: yes, a short one in the help centre with only what they can see, updated weekly.
- The interface still says Brew in a few places, now from one constant. Do we set that constant to the picked name, or to none, before the five partners use it daily? Proposal: keep Brew until the name is picked, then change the one line.
- Who decides the compute service account rights? Proposal: Param removes the project wide rights this week and gives each service its own account.