Heartbeat Action Query Not Sent to Source

Hello lyancy 

welcome to this Fabric community forum.

You want to enter the heartbeat query for this PostgreSQL connection:

This query depends on a table in the source database, as you mentioned already.

The documentation does not provide a real sample:

I have no hands-on experience with this database, but I did some research that could help you out.

It seems your solution should work because it looks a lot like this idempotent call:

CREATE TABLE public.test_heartbeat_table (
    id integer primary key,
    last_seen timestamptz not null
);

INSERT INTO public.test_heartbeat_table (id, last_seen)
VALUES (1, now());

[idempotent call]
UPDATE public.test_heartbeat_table
SET last_seen = now()
WHERE id = 1;

A simplified alternative table and call could look like:

CREATE TABLE public.test_heartbeat_table (
    id bigserial primary key,
    text text not null,
    created_at timestamptz not null default now()
);

INSERT INTO public.test_heartbeat_table (text)
VALUES ('test_heartbeat');

I found this post, which could be linked. There, a more elaborate solution is proposed:

INSERT INTO my_schema.fabric_heartbeat (id, heartbeat_ts) 
VALUES (1, NOW()) 
ON CONFLICT(id) 
DO UPDATE SET heartbeat_ts = EXCLUDED.heartbeat_ts;

These are three possible solutions that could hopefully point you in the right direction.

Please let us know which actually works for you.

---

If this answer helps you, marking it as the accepted answer is appreciated. All community members with similar questions will benefit by doing so. Your contribution is highly appreciated.

Thankyou, svelde for your response.

Hi lyancy,

We appreciate your inquiry through the Microsoft Fabric Community Forum.

We would like to inquire whether have you got the chance to check the solution provided by svelde to resolve the issue. We hope the information provided helps to clear the query. Should you have any further queries, kindly feel free to contact the Microsoft Fabric community.

Thank you.

Hi,

Your heartbeat table and UPDATE statement look correct, so if the Eventstream is running without errors but the heartbeat query is never executed, it may not be a SQL issue.

A few things I'd recommend checking:

• Verify that Heartbeat is actually enabled for the PostgreSQL CDC source and that the heartbeat interval is configured as expected.

• Confirm that the PostgreSQL user configured for CDC has sufficient permissions to execute the UPDATE statement on the debezium_heartbeat table.

• Check whether the heartbeat action is only triggered when the connector is actively polling for changes. If there is no CDC activity, the connector's behavior may differ depending on the implementation.

• Review the Eventstream logs (if available) and PostgreSQL logs to see whether the heartbeat query is being attempted or skipped entirely.

To help narrow it down:

• Which PostgreSQL version are you using?

• Is the source Azure Database for PostgreSQL or self-managed PostgreSQL?

• Does normal CDC capture work correctly, with only the heartbeat action failing?

If everything is configured correctly and the heartbeat query is still never reaches the source, this may be a product issue. In that case, I'd recommend opening a Microsoft Support ticket with:

• Workspace and Eventstream details

• PostgreSQL version

• Source type

• Connector configuration

• The heartbeat interval and action query

• Relevant timestamps

If Microsoft identifies the root cause or provides a workaround, please consider sharing it here. It would be very helpful for others using PostgreSQL CDC with Eventstream heartbeat actions.

If you found this reply helpful, please consider giving it a Kudos. If it helps resolve your issue, marking it as the Accepted Solution will help other community members facing the same problem.