Operations investigation
Dashboard → logs → queue → trace → resolve
Home dashboard · account acme-ops · 06:42
Failed workflow runs (2)
nightly_erp_sync · VALIDATION_ERROR · 02:14
vendor_intake_submit · TIMEOUT · 04:55
Unread notifications (3)
Connection rate limit warning · hubspot-marketing
open AI tasks: 1 · quick link → ops console
Built to be operated
“Build in Tealfabric. Run in Tealfabric. See it all in Tealfabric.”
Platform
Platform operations — see what’s running and why
When failures span workflows and connections, the operations console and job queues show what ran and why—dashboard alerts, searchable logs, AI approvals, and connection history on one account.
Adoption context
- You need this when
- Failures across workflows and connections must show in one operations view—not scattered logs, inboxes, and one-off scripts.
- Often bundled with
- Integrations for live workflows on one platform.
- Not required if
- You are wiring a single workflow first—expand operations-console triage when connection or workflow volume justifies it.
Related workflow: Failed sync detection and retry · Adoption path
When something breaks at 2 a.m., you start in one place and follow the thread across queues, logs, and execution history.
Distributed automation usually means distributed confusion—workflow failures in one tool, connection errors in another, webhook issues with no request log, data changes with no history, and AI costs with no visibility.
Tealfabric gives operators one operational layer woven into the same workspace where teams design workflows, connect systems, and publish apps—not a separate monitoring product bolted on.
- Built to be operated—not only configured; every major capability leaves an account-scoped trail
- One place to follow the thread from dashboard check to operations console deep dive
- Nine log types, workflow and connection queues, and worker throughput in one console
- Cancel stuck jobs, re-run workflows, and retry connections—act, don't just watch
- Run history in workflows, connections, and WebApps where work was defined
- Datapool change log and security logs in the same operational layer
- AI call logs with tokens, cost, response times, and 24-hour health alerts
- Queue status API for external async polling; structured errors for alerts and retries
Day-to-day operations
From morning health check to integration incident and audit request.
Investigation flow
Dashboard alert → operations logs → queue action → follow the thread → fix and re-run.
A nightly ERP sync fails at 2 a.m. The dashboard surfaces the failure. Step logs in the operations console reveal a validation error on row 847. Operators inspect the workflow and connection queues, follow the link across Datapool change log, patch the step, re-run, and confirm notification delivery.
Operations investigation
Dashboard → logs → queue → trace → resolve
Home dashboard · account acme-ops · 06:42
Failed workflow runs (2)
nightly_erp_sync · VALIDATION_ERROR · 02:14
vendor_intake_submit · TIMEOUT · 04:55
Unread notifications (3)
Connection rate limit warning · hubspot-marketing
open AI tasks: 1 · quick link → ops console
03 · Capabilities
One pane for operations—act, don't just watch.
Investigate in the operations console; fix in context where the work was defined. Everything filtered by account—operators see their organization's activity.
Open the platform and see what needs action. Unread alerts, recent queue failures with error snippets, and quick links to dig deeper in one click—not a static link farm.
failed runs (2)
notifications (3)
open AI tasks
Morning snapshot—notifications, failed workflows, and open AI tasks.
04 · Console log types
Nine searchable log types in one operations console.
Workflow runs, steps, connections, connectors, Datapool changes, security, AI calls, notification delivery, and WebApp requests—searchable, sortable, and paginated.
- 01
Workflow runs
Run ID, status, duration, errors
- 02
Workflow steps
Step-level log output from automation code
- 03
Connections
Connection run queue—status, timing, failures
- 04
Connectors
Connector-level execution records
- 05
Datapool change log
Schema actions, queries, inserts and updates with context
- 06
Security
Sign-in and security events—IP, user, severity
- 07
AI calls
AI request status, tokens, cost, errors
- 08
Notification delivery
Channel, recipient, delivered or failed status
- 09
WebApp
Request method, response status, duration, linked workflow
05 · Operational layers
Visibility where work is defined—and where operators start each day.
Dashboard for the morning check, operations console for cross-cutting search, then feature-level history in ProcessFlow, integrations, WebApps, and Datapools.
- Dashboard
Morning check and alerts—start here each day
- Operations console
Search, queues, workers, cross-cutting logs
- ProcessFlow
Run history, step logs, analytics, artifacts
- Integrations
Queue, history, connector logs
- WebApps
Request-level execution log
- Datapools
Change log for queries and updates
- Documents
Review history
- Notifications
Delivery confirmation
- Org settings
Usage and billing
Ops console · log stream
nine searchable types · filter · paginate
Workflow runs
status:failed · last 24h
[ERROR] nightly_erp_sync · VALIDATION_ERROR
pf_run_a91c · 4.2s
[WARN] vendor_intake_submit · TIMEOUT
pf_run_b42d · 30.1s
Simulated — one console, every log type your operators need
06 · Platform connections
Fits the platform
Visibility maps to how work actually flows—trigger, queue, worker execution, logs, and dashboard. ProcessFlow, connections, WebApps, Datapools, AI, and notifications all leave trails you can search, sort, and act on.
Operate with confidence
See the operations console, queues, and run history across your account.
We walk through dashboard checks, nine log types, queue cancel and re-run, Datapool change log, AI ops metrics, and notification delivery—on the same platform as your automation.
Pilots start with one live workflow—system connections, steps, and full history.