Quick question - Meltano/Airflow/Custom Tap with state - at the end of a previous sync my tap recorded the start successfully. the bookmarked timestamps to work with incremental pulling of data from the source. When the next sync starts the Meltano-DB job table shows a payload of an empty

{}

. Is this by design that it has started the job but not pulled in the previous state yet? Or should I be looking for something else.

@ryan_allen The

job

record's

singer_payload

contains only the state output by the target (which it was sent from the tap), not the initial state provided to the tap, so you'd expect it to be empty on a running job until the target emits its first state message

Perfect that is what I wanted to hear - Thanks!!