1.4版本 AT模式 服务中undo_log数据不会有数据而且直接执行了

saas-app ---调用--> financial-server

saas-app seata的启动日志 resourceIds='null'
i.s.c.r.n.NettyPoolableFactory NettyPool create channel to transactionRole:RMROLE,address:172.30.16.183:8091,msg:< RegisterRMRequest{resourceIds='null', applicationId='yibanapp', transactionServiceGroup='yibanapp-seata-service-group'} >
[10:35:32] [timeoutChecker_2_1] [INFO ] i.s.c.r.n.RmNettyRemotingClient register RM success. client version:1.4.0, server version:1.5.0-SNAPSHOT,channel:[id: 0xa79715fc, L:/172.30.16.183:63531 - R:/172.30.16.183:8091]
[10:35:32] [timeoutChecker_2_1] [INFO ] i.s.c.r.n.NettyPoolableFactory register success, cost 18 ms, version:1.5.0-SNAPSHOT,role:RMROLE,channel:[id: 0xa79715fc, L:/172.30.16.183:63531 - R:/172.30.16.183:8091]

financial-server
i.s.c.r.n.NettyPoolableFactory NettyPool create channel to transactionRole:TMROLE,address:172.30.16.183:8091,msg:< RegisterTMRequest{applicationId='financial', transactionServiceGroup='yibanapp-seata-service-group'} >
[10:30:33] [timeoutChecker_1_1] [INFO ] i.s.c.r.n.TmNettyRemotingClient register TM success. client version:1.4.0, server version:1.5.0-SNAPSHOT,channel:[id: 0xaecbafe3, L:/172.30.16.183:63004 - R:/172.30.16.183:8091]
[10:30:33] [timeoutChecker_1_1] [INFO ] i.s.c.r.n.NettyPoolableFactory register success, cost 22 ms, version:1.5.0-SNAPSHOT,role:TMROLE,channel:[id: 0xaecbafe3, L:/172.30.16.183:63004 - R:/172.30.16.183:8091]

saas-app 与 financial-server的transactionServiceGroup我设置的是一样的
enable-auto-data-source-proxy: true 一样的
tx-service-group: yibanapp-seata-service-group 这个也是一样的 saas-app financial-server

我在saas-app加入@GlobalTransactional 程序正常执行，但是 financial-server 服务直接把数据插入库中了，undo_log数据没有数据？不知道为啥

Start by reproducing the transaction across saas-app and financial-server using the configurations and registration logs in the report. Check the data-source proxy, transaction service group, and undo_log behavior in both services. Done means the cause of the direct commit is identified and the reported transaction produces the expected undo_log entry or a documented configuration error.

Written by the indexing model from the issue text.