Hi everyone. We're attempting to do some additional data processing using JHooks, sending those events to a custom Lambda. We'd like to be able to correlate these events to the Job that triggered them. We can see in the data that gets sent to the lambda, there's a place for "job" and "parentJob" wh…

The job IDs made for test mode are most likely just dummy samples, which is why you wouldn't find them in your /jobs endpoint. Out of curiosity, do you have any branching in your flow? If not, can you add a dummy branch anywhere in the flow and then see if it shows up during runtime?

Ah, that would definitely explain why we can't find the test mode ones. Any idea why they wouldn't show up when test mode is off? We don't have any branching. Just a Shopify request, then two HTTP Posts as sequential imports. What would the dummy branch do for us? Not totally clear there.

Job ID in JHooks Sent to Lambda

Integrator.io

tylerlamparter (Tyler Lamparter) May 1, 2025, 8:39pm 4

Branching forces the flow to run on a newer runtime engine where it should be available.

Issue with Logging Job Details During Script Execution in Flow

Topic		Replies	Views
Issue with Logging Job Details During Script Execution in Flow Integrator.io javascript , flow-builder	5	193	May 23, 2025
Parent Job Failed Integrator.io error-handling	1	136	February 27, 2025
Which case Data is ignoring Integrator.io flow-builder , hooks	5	130	August 1, 2023
Test mode does not pass mock data through branching JavaScript step Integrator.io flow-builder	9	163	August 7, 2026
Celigo Flow Log Dashboard Integrator.io	4	134	December 3, 2025

Job ID in JHooks Sent to Lambda

Related topics