turbo-operations
Original:🇺🇸 English
Translated
1 scripts
Turbo pipeline operations reference — lifecycle commands (pause, resume, restart, delete), pipeline states, checkpoint behavior, streaming vs job-mode differences, CLI syntax for `inspect`/`logs`, TUI shortcuts, and error pattern lookup. Triggers on: 'how do I pause/restart/delete', 'will deleting lose my data', 'what does this error mean', 'inspect TUI shortcuts'. For interactive diagnosis of a broken pipeline, use /turbo-doctor.
13installs
Sourcegoldsky-io/goldsky-agent
Added on
NPX Install
npx skill4agent add goldsky-io/goldsky-agent turbo-operationsTags
Translated version includes tags in frontmatterSKILL.md Content
View Translation Comparison →Turbo Pipeline Operations
Lifecycle commands, monitoring, and error reference for running Turbo pipelines. This is a lookup reference — for interactive troubleshooting of a broken pipeline, use . For building new pipelines, use .
/turbo-doctor/turbo-builderPipeline States
| State | Description |
|---|---|
| running | Pipeline is actively processing data |
| starting | Pipeline is initializing |
| paused | Pipeline is paused (replicas set to 0) |
| stopped | Pipeline is not running (manually stopped) |
| error | Pipeline encountered an error |
| completed | Job-mode pipeline finished processing range |
Streaming vs Job Mode Lifecycle
| Operation | Streaming Pipeline | Job-Mode Pipeline ( |
|---|---|---|
| List | Shows as | Shows as |
| Pause | Supported | Not supported |
| Resume | Supported | Not supported |
| Restart | Supported | Not supported — use delete + apply |
| Delete | Supported | Supported (auto-cleanup ~1hr after done) |
| Apply | Updates in place | Must delete first, then re-apply |
Job-Mode Pipeline Lifecycle
Job-mode pipelines () are one-time batch processes:
job: true- Start — process data from to
start_atend_block - Run — process the bounded data range
- Complete — automatically stop when range is processed
- Auto-cleanup — ~1 hour after completion, automatically removed
Cannot pause, resume, or restart. Must delete before redeploying.
Lifecycle Commands
List Pipelines
bash
goldsky turbo listPause a Pipeline
Temporarily stop processing without deleting. Preserves all state for later resumption.
bash
goldsky turbo pause <pipeline-name>Resume a Pipeline
Restore a paused pipeline. Can only resume a paused pipeline.
bash
goldsky turbo resume <pipeline-name>Restart a Pipeline
Trigger a pod restart for a running or paused pipeline.
bash
goldsky turbo restart <pipeline-name>
# To clear all checkpoints and reprocess from the beginning:
goldsky turbo restart <pipeline-name> --clear-stateDelete a Pipeline
Permanently remove a pipeline. All checkpoints are lost. Data already written to sinks is preserved.
bash
goldsky turbo delete <pipeline-name>Delete and Recreate (Fresh Start)
bash
goldsky turbo delete my-pipeline
goldsky turbo apply my-pipeline.yamlCheckpoint Behavior
- Deleting a pipeline removes its checkpoints permanently
- Recreating with the same name starts fresh (no checkpoint recovery)
- To preserve checkpoints, use to update instead of delete/recreate
apply - Checkpoint state is tied to source names — renaming a source resets its checkpoint
- Checkpoint state is tied to pipeline names — renaming a pipeline resets all checkpoints
Monitoring Commands
| Action | Command |
|---|---|
| List pipelines | |
| View live data | |
| Inspect specific node | |
| View logs | |
| Follow logs | |
| Logs with timestamps | |
| Last N lines | |
| Logs since N seconds ago | |
Live Inspect TUI Shortcuts
| Key | Action |
|---|---|
| Next/prev tab |
| Jump to tab number |
| Scroll |
| Top/bottom |
| Scroll by page |
| Search |
| Next/prev match |
| Clear search |
| Toggle definition |
| Open web dashboard |
| Open web editor |
| Quit |
| Select and copy text |
The TUI automatically reconnects when the pipeline is updated, paused, resumed, or temporarily unavailable. It has a 30-minute timeout before closing.
Log Analysis Script
Use the helper script to quickly analyze pipeline logs:
bash
./scripts/analyze-logs.sh <pipeline-name>
./scripts/analyze-logs.sh <pipeline-name> --tail 100The script checks for common error patterns and reports findings with recommendations.
Common Error Patterns
Detailed error patterns and solutions are in.data/error-patterns.json
| Error Pattern | Likely Cause | Fix |
|---|---|---|
| Database unreachable | Check network/firewall settings |
| Wrong credentials | Update secret with correct credentials |
| Missing secret | Create secret with |
| Invalid transform SQL | Fix SQL in YAML and redeploy |
| Primary key collision | Ensure unique primary key in transform |
| TypeScript runtime failure | Check script logic, null handling, return types |
| Backend connection issue | Verify dynamic table secret/table exists |
| Script crash in sandbox | Debug script — check for undefined access |
| External HTTP endpoint slow | Increase |
Script Transform Issues
| Issue | Fix |
|---|---|
| Add null checks: |
| Wrong return type | Ensure returned object matches |
| Missing return fields | All |
| Ensure script defines |
| BigInt errors | Use |
Dynamic Table Issues
| Issue | Fix |
|---|---|
| Table not found | Create the table in PostgreSQL before deploying |
| No matches from check | Verify data exists in the backing table |
| Stale data | For postgres backend, verify rows are actually there |
| Memory pressure | Large in_memory tables → switch to postgres backend |
Troubleshooting Quick Reference
| Symptom | Likely Cause | Quick Fix |
|---|---|---|
| No data flowing | | Wait for new data or use |
| Auth failed | Wrong credentials | Update secret with correct password |
| Connection refused | Network/firewall | Check host, whitelist Goldsky IPs |
| Storage exceeded | Neon free tier (512MB) | Upgrade plan or clear data |
| SQL error | Bad transform syntax | Validate YAML first |
| Pipeline not found | Name mismatch | Run |
| Permission denied | Role insufficient | Verify Editor or Admin role in the project |
| Job-mode stale | Delete first, then re-apply |
| Cannot pause/resume job | Job-mode limitation | Job pipelines don't support pause/resume |
| Cannot restart job | Job-mode limitation | Delete + re-apply instead |
| Can't connect to inspect | Pipeline not running | Check status with |
| Logs are empty | Pipeline just started | Wait for data or check |
| TUI disconnects | Pipeline interrupted | Auto-reconnects within 30 min; check status |
Related
- — Interactive diagnostic skill for pipeline issues
/turbo-doctor - — Build and deploy new pipelines
/turbo-builder - — YAML configuration and architecture reference
/turbo-pipelines