issues Search Results · language:Dune language:Python language:JavaScript language:PHP language:JavaScript language:CSS
Filter by
47.9M results
Part of #355.
Problem
The capability spans a new DSL, two editors, triggers, and an internal Temporal deployment — unusable by tenants and
unmaintainable by operators without documentation.
Proposed ...
cap:workflows
documentation
enhancement
P2
andrea-mucci
Part of #355.
Problem
The full loop must be proven against a real deployed stack, per the repo s E2E conventions, before the capability ships.
Proposed solution
New spec group under tests/e2e/ (own ...
cap:workflows
enhancement
P2
Part of #355.
Problem
Tenants must observe executions live — per-node status on the canvas, streaming history, run lists — and act (retry,
cancel, approve) without operator involvement.
Proposed solution ...
cap:workflows
enhancement
P2
Part of #355.
Problem
Published flows must start without manual action: on a schedule, on an inbound webhook, or on platform events — none of
which is wired.
Proposed solution
All trigger registration ...
cap:workflows
enhancement
P2
Summary
analytics-api runs a one-shot schema validator at startup that probes every metric_key against ClickHouse and caches the
result on the catalog row (metric_catalog.schema_status / schema_error_code). ...
bug
cyberantonz
Part of #355.
Problem
Power users need a text-first editing experience, and the canvas and YAML must be two synchronized views of one
definition — with YAML as the single source of truth.
Proposed solution ...
cap:workflows
enhancement
P2
The following repos aren t configured in site-config.json yet:
- [ ] brad-funeral — add to showcase, order, hidden, or manual_entries
- [ ] breed-and-speed — add to showcase, order, hidden, or manual_entries ...
jkraybill
Part of #355.
Problem
Tenants need to compose flows visually; the web console (apps/web-console: React 18 + Vite + TS + Tailwind/Radix) has no
canvas tooling.
Proposed solution
A new Flows section ...
cap:workflows
enhancement
P2
Part of #355.
Problem
The cardinal risk of a multitenant workflow engine is cross-tenant leakage — via Temporal visibility queries, task
queues, workflow IDs, activity credentials, or noisy-neighbor ...
cap:workflows
enhancement
P1
security
tenant-isolation
Part of #355.
Problem
Everything the console does must go through Falcone s own API; no tenant ever talks to Temporal. There is currently no
flow CRUD, publish, or execution-control surface.
Proposed ...
cap:workflows
enhancement
P1
tenant-isolation
Learn how you can use GitHub Issues to plan and track your work.
Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub IssuesProTip! Restrict your search to the title by using the in:title qualifier.
Learn how you can use GitHub Issues to plan and track your work.
Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub IssuesProTip! Restrict your search to the title by using the in:title qualifier.