Forum Discussion
ABW - No ContractActionParameter audits recorded in SQL Database when using REST or Messaging APIs
You may have missed something with the configuration. Please feel free to send me your config and solidity to zeyadr [at] microsoft [dot] com
The samples for UI, RestAPI and message based Action creation above are from the same application (the Hello Workbench sample). But you're right, according to the architecture diagram all commands flow across the activityHub Service Bus queue, so unless the UI is breaking architecture and writing to the Sql database, there must be something different in my UI, and the Rest / Direct message based actions.
I'll temporarily turn off my the Worker VM and dissect the messages placed on the Service Bus by the UI vs the ones I'm creating.
Let me know what you find, or send me an email and we can help debug.
My understanding of the ABW architecture was wrong - the REST API (and possibly the UI) also apparently write to the Sql Database, in advance of sending messages to the worker via the Service Bus, so when using the Messaging API, you would need to either subscribe to the Event Grid or poll the Sql database, in order to locate the Contract Id (on create) and Contract Action Id (on transactions), which then needs to be provided on further contract interactions when using the Service Bus messaging approach.