inaccurate display of last sync after adding a new connection to an existing pipeline

[jakejh]

See attached. the gsheet connection was just created and added to the same pipeline as the other two connections, but it has not been run.

[fatchat]

Yes this is a bug, it thinks it was run because the pipeline it's now a part of was run

This is a design flaw, will need to figure out a solution

[jakejh]

I just noticed a related behavior: the connection below was part of a pipeline that had been running daily for the last month, but I deleted the pipeline today. prior to deleting the pipeline, dalgo said the last sync was 20 hours ago. now, apparently because the pipeline no longer exists, it says the last sync was 10 days ago, which is probably when I last ran a manual sync.

[fatchat]

your guess is correct - dalgo looks through the list of manual syncs and pipeline runs for pipelines this connection is a part of (these lists are managed separately as distinct prefect deployments)

the change we need to implement is to look directly at the airbyte history rather than the prefect history