Impulse Dev Manual
HomePricingContact Us
  • Understanding Impulse Sync
  • Understanding how Impulse diffs content
  • Understanding Job Scheduling
  • Motation
    • Content Motation
    • Definition Motation
    • Domain Motation
    • Folder Motation
    • Language Motation
    • Relationship Motation
    • Tag Motation
  • Connectors
    • Source Connector
    • Destination Connector
    • Go Code
    • IDs
    • ID Mapping
    • Testing Controller
      • Implementation
  • Motators Binary
    • Implementation
    • Go Code
  • Services
    • Connector Depot
    • Motator Binary Depot
    • Job Depot
    • Endpoint Depot
    • Sync Manager
    • Content Diffuser
    • Pickup Taxi
    • Dropoff Taxi
    • Pipeliner
    • Scheduler
    • Motator
    • Motator Service
  • Watchdog Process
    • Watchdog flow
  • Impulse License
  • Troubleshooting
    • Job Config
    • Transaction Audit Trail
  • gRPC
    • Protocol buffer compiler
  • Test Commands
  • Glossary
Powered by GitBook
On this page
  • Changes to job config
  • Start transaction options

Was this helpful?

  1. Troubleshooting

Job Config

Changes to job config

Every save to a job is stored in cassandra table that can be queried. Howver, there is no exposed rest API for this at the moment.

Start transaction options

If a job is run with start transaction options, the job that was used can be found in the transaction messages postgres table. This table is archived after a transation finishes. To access it, download the archive from the postgres container and extract it.

Postgres archived tables are temporal/ephemeral. Meaning they will be deleted. When the postgres container restarts, they will be removed. Or after 1 week they will be removed.

PreviousTroubleshootingNextTransaction Audit Trail

Last updated 1 year ago

Was this helpful?