You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
finding: platform-checklist notes from the integration-system run (sys_account 405, Studio flow read-only, email wire-keys, predicate multi over REST) #7745
Consolidated "Notes worth keeping" from the run that are checklist / recording notes rather than standalone product defects. (The seed-data non-user assignment and the push-success-while-nothing-delivered gap are judged real defects and split into their own cards.)
POST /api/v1/data/sys_account now answers 405 (create not allowed), so the previously-used recipe for turning a seeded demo persona into a real login is closed on this build.
A flow authored over the metadata API is not editable in Studio — with or without ?package=, it opens behind "This flow is provided by an installed package, so it is read-only at runtime". ResourceEditPage treats an item as artifact-backed when layered.code != null && _packageId !== 'sys_metadata', and flow declares allowOrgOverride:false; the editable path is the console's own create page.
Checklist slip — email-template-render clause 7 names a {to, subject, bodyHtml} message body, but the wire keys are html / text (bodyHtml is the template field). The literal shape the clause names is refused 400 "at least one of text or html is required". The checklist clause should be corrected.
Predicate (multi:true) writes are unreachable over REST by design (deleteManyData 把请求体的 options 展开在 where 之后 —— body 可覆盖 id 谓词,把"删这几条"放大成"删调用者可见的全部" #3897 strips options.multi from the batch routes), so the bulk-webhook clause needs a flow update_record / delete_record node with multi:true fired through the api trigger. Recorded so the next sweep does not re-derive it.
Root cause
Recording notes for the platform-checklist / docs; each is attributed inline above. There is no single code root cause — the actionable items are a checklist clause correction (email wire-keys) and two behaviours worth documenting (sys_account 405, Studio read-only for metadata-API flows).
Reproduction
Not applicable — these are recorded observations from the run for the platform-checklist maintainers; each note names the surface it was observed on.
Source
Extracted from the QA run #7690 (framework 92f26f7, console 09987b680).
Symptom
Consolidated "Notes worth keeping" from the run that are checklist / recording notes rather than standalone product defects. (The seed-data non-user assignment and the push-success-while-nothing-delivered gap are judged real defects and split into their own cards.)
POST /api/v1/data/sys_accountnow answers 405 (create not allowed), so the previously-used recipe for turning a seeded demo persona into a real login is closed on this build.?package=, it opens behind "This flow is provided by an installed package, so it is read-only at runtime".ResourceEditPagetreats an item as artifact-backed whenlayered.code != null && _packageId !== 'sys_metadata', andflowdeclaresallowOrgOverride:false; the editable path is the console's own create page.email-template-renderclause 7 names a{to, subject, bodyHtml}message body, but the wire keys arehtml/text(bodyHtmlis the template field). The literal shape the clause names is refused 400 "at least one of text or html is required". The checklist clause should be corrected.multi:true) writes are unreachable over REST by design (deleteManyData把请求体的options展开在where之后 —— body 可覆盖 id 谓词,把"删这几条"放大成"删调用者可见的全部" #3897 stripsoptions.multifrom the batch routes), so the bulk-webhook clause needs a flowupdate_record/delete_recordnode withmulti:truefired through the api trigger. Recorded so the next sweep does not re-derive it.Root cause
Recording notes for the platform-checklist / docs; each is attributed inline above. There is no single code root cause — the actionable items are a checklist clause correction (email wire-keys) and two behaviours worth documenting (sys_account 405, Studio read-only for metadata-API flows).
Reproduction
Not applicable — these are recorded observations from the run for the platform-checklist maintainers; each note names the surface it was observed on.
Source
Extracted from the QA run #7690 (framework 92f26f7, console 09987b680).