Guide
Outbound Sync Jobs
Outbound sync uses connection setup from the app UI. CLI does not create or map connections; it executes and inspects runs for the tenant.
Core outbound commands
abm-warranty connections list --tenant-id <TENANT_ID>
abm-warranty connections test --tenant-id <TENANT_ID> --connection-id <CONNECTION_ID>
abm-warranty connections remove --tenant-id <TENANT_ID> --connection-id <CONNECTION_ID>
abm-warranty connections show-jobs --tenant-id <TENANT_ID>Run outbound now
abm-warranty connections run --tenant-id <TENANT_ID> --type full
abm-warranty connections run --tenant-id <TENANT_ID> --type single --serial C02FC149MD6TOutbound behavior notes
- Run order and connection set are loaded from saved UI binding/order for that tenant.
- Source mode is loaded from saved connection configuration.
- Use Ctrl+C to cancel active runs.
- If a command fails with
--tennant-id, use--tenant-id.
Outbound success/failure interpretation
| CLI Output Pattern | Meaning | Primary Next Check |
|---|---|---|
[ConnectionsCLI] completed run=... status=completed |
Outbound run completed | Inspect connections show-jobs for per-connection results |
[ConnectionsCLI] failed: ... |
Run terminated by request/contract/payload error | Validate contract method/formatter and mapping field paths |
error: no runnable connection set is configured... |
No saved mapped connection set for tenant | Configure mapped connections in app UI first |