Hi folks, I have an issue where

self.get_starting_timestamp

is only returning the default config

start_date

I set and not the

replication_key_signpost

value from the previous run. Has anyone seen this issue where Meltano will show the correct value for the

replication_key_signpost

, but not read it as the

starting_replication_value

? This is the state emitted right when the sync starts. Note how

replication_key_signpost

>

starting_replication_value

{
  "type": "STATE",
  "value": {
    "bookmarks": {
      "agent_summary": {
        "replication_key_signpost": "2022-09-08T18:26:08.276635+00:00",
        "starting_replication_value": "2022-09-03"
      }
    }
  }
}

self.get_starting_timestamp

returns "2022-09-03" Then at the end of the sync this message gets emitted, even though data was loaded through the correct end_date:

{"type": "STATE", "value": {"bookmarks": {"agent_summary": {}}}}

Hi @avishua_stein, looks like a 🐛! So, to be clear, the stream doesn’t have a proper

replication_key

and you’re trying to rely on the signpost to create a bookmark?

@edgar_ramirez_mondragon the stream does have a proper replication key, I thought that the same process which generated the

replication_key_signpost

would also assign that value as a bookmark. I'm thinking about creating the bookmark manually though since I can't figure out what's wrong. If it's relevant, the stream doesn't have a primary key