Essentially, if you run npx dbos debug -u <workflow UUID> without specifying a proxy, the code can pull workflow status from the specified Postgres in the dbos-config.yaml file. This mode doesn't allow you to step through transactions, but can easily debug workflows and view outputs from transactions and communicators.
This feature is to mainly support debugging with local Postgres installation, because this mode doesn't try to connect to the cloud provenance DB.
We recently added a capability in DBOS Transact to support stepping through a workflow without a debug proxy. Docs: https://github.com/dbos-inc/dbos-docs/pull/109 Transact: https://github.com/dbos-inc/dbos-transact/pull/379
Essentially, if you run
npx dbos debug -u <workflow UUID>without specifying a proxy, the code can pull workflow status from the specified Postgres in the dbos-config.yaml file. This mode doesn't allow you to step through transactions, but can easily debug workflows and view outputs from transactions and communicators.This feature is to mainly support debugging with local Postgres installation, because this mode doesn't try to connect to the cloud provenance DB.