unexpected error while forging log: not found when running v2CreateBulk operation from generated openapi typescript sdk

[V-ed]

Hi!

While I'm not sure how much the openapi support is available and not given given as a "here it is, have fun with it", I'm trying to understand how could such an issue happen because the request I'm sending seem to be working, but I'm getting a ledger error.
In other words, maybe you guys have an idea on what could be happening here since I'm not sure how the internals of the ledger works :)

---

When running a v2CreateBulk request through an api testing tool (Bruno in our case), the endpoint works perfectly as expected.

When running the same query through a sdk generated from your openapi specs, I'm getting the error in the title :

unexpected error while forging log: not found

Just to make the proper direction clear : I copied the request that was running through our own code through the openapi generated sdk, copied the body, then pasted and tried it in Bruno and that worked, so the issue is at the sdk level.

Essentially, we seem to be hit by this line :

https://github.com/formancehq/ledger/blob/82f6822c8ed6a964b0e14b2f98f62f5a715c2670/internal/controller/ledger/log_process.go#L125

Just for information since I don't want you guys to debug our sdk

we are using npx -y @openapitools/openapi-generator-cli version-manager set 6.6.0

templateDir: openapi-ts-template
generatorName: typescript-node
inputSpec: openapi.yaml
additionalProperties:
  npmName: 'ledger-sdk'
  supportsES6: true
files:
  README.md: {}
  .prettierignore: {}
  turbo.json: {}

However, while debugging, since it seems the request is essentially the same (I debugged the internals, but I could have missed something), my question essentially boils down to :

What could be the reasons for an error about forging logs happening while doing a bulk request?

Our generated sdk also works for other api endpoints, it seems to only happen to the v2CreateBulk endpoint.

Any pointers would help, thanks a lot! :)

[gfyrag]

Hello!
Strange error.
What is your ledger version?

If you have opentelemetry traces enabled, you should have a more precise error regarding the failing request.

[V-ed]

For the ledger version, we are currently on v2.2.45, but I also tested using v2.2.48 and v2.3.1, all of which had the same issue (I should note I used the openapi file from v2.2.47 when testing with v2.2.48 since .48 does not have the openapi.yml file in the releases).

There is this weird error in the ledger container logs when the issue happens :

time="2025-10-28T16:12:42Z" level=debug msg="WITH \"upd\" AS (UPDATE \"_default\".transactions SET reverted_at = (now() at time zone 'utc'), updated_at = (now() at time zone 'utc') WHERE (id = 0) AND (reverted_at is null) AND (ledger = 'ledger') RETURNING *) SELECT * FROM ((SELECT upd.*, true as modified FROM upd) UNION ALL (SELECT *, false as modified FROM \"_default\".transactions WHERE (id = 0 and ledger = 'ledger') LIMIT 1)) transactions LIMIT 1" component=bun duration=2.022ms err="sql: no rows in result set" operation=SELECT trace-id=z1v5CDIh9R

time="2025-10-28T16:12:42Z" level=debug msg="ROLLBACK TO SAVEPOINT SP_b2f80955987b1cb87e8232f6c604" component=bun duration="117µs" operation=ROLLBACK trace-id=z1v5CDIh9R

the sql: no rows in result set is weird to me, the ids we are passing work when using the exact same query in Bruno

I don't want to assume the requests are exactly the same however, but the body should be the same

[formance-support[bot]]

I just noticed you have a “where id = 0” in your sql request.
As transactions ids start to 1, I guess you pass 0 in your bulk request. Can you check the request made by the sdk?

[aalloiteau]

HI @V-ed were you able to move forward we the above ?

[V-ed]

Hi! Terribly sorry for the delay before replying, I got stuck in other priorities, but I'm on the lookout to try this request again in the generated sdk soon (might try today or early next week)

Will update here shortly! And thanks for the follow-up too!

[V-ed]

Hi! Well this is awkward for the delay it took me to come back into this issue, but after finally coming back to it, I did a more thorough investigation and realized that our openapi generator caused issues with models that have oneOf as their key, such as your v2BulkElement model :

    V2BulkElement:
      type: object
      oneOf:
        - $ref: '#/components/schemas/V2BulkElementCreateTransaction'
        - $ref: '#/components/schemas/V2BulkElementAddMetadata'
        - $ref: '#/components/schemas/V2BulkElementRevertTransaction'
        - $ref: '#/components/schemas/V2BulkElementDeleteMetadata'
      discriminator:
        propertyName: action
        mapping:
          CREATE_TRANSACTION: '#/components/schemas/V2BulkElementCreateTransaction'
          ADD_METADATA: '#/components/schemas/V2BulkElementAddMetadata'
          REVERT_TRANSACTION: '#/components/schemas/V2BulkElementRevertTransaction'
          DELETE_METADATA: '#/components/schemas/V2BulkElementDeleteMetadata'

basically, our generator generated this :

ledger-sdk/model/v2BulkElement.ts

/**
 * Ledger API
 * No description provided (generated by Openapi Generator https://github.com/openapitools/openapi-generator)
 *
 * The version of the OpenAPI document: v1
 *
 *
 * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
 * https://openapi-generator.tech
 * Do not edit the class manually.
 */

import { RequestFile } from './models'
import { V2BulkElementAddMetadata } from './v2BulkElementAddMetadata'
import { V2BulkElementCreateTransaction } from './v2BulkElementCreateTransaction'
import { V2BulkElementDeleteMetadata } from './v2BulkElementDeleteMetadata'
import { V2BulkElementDeleteMetadataAllOfData } from './v2BulkElementDeleteMetadataAllOfData'
import { V2BulkElementRevertTransaction } from './v2BulkElementRevertTransaction'

export class V2BulkElement {
  'action': string
  'ik'?: string
  'data'?: V2BulkElementDeleteMetadataAllOfData

  static discriminator: string | undefined = 'action'

  static attributeTypeMap: Array = [
    {
      name: 'action',
      baseName: 'action',
      type: 'string',
    },
    {
      name: 'ik',
      baseName: 'ik',
      type: 'string',
    },
    {
      name: 'data',
      baseName: 'data',
      type: 'V2BulkElementDeleteMetadataAllOfData',
    },
  ]

  static getAttributeTypeMap() {
    return V2BulkElement.attributeTypeMap
  }
}

emphasis on the following lines :

    {
      name: 'data',
      baseName: 'data',
      type: 'V2BulkElementDeleteMetadataAllOfData',
    },

the generated sdk serializer then always tried to serialize any operation as an V2BulkElementDeleteMetadataAllOfData, rendering our operations essentially useless (since we didn't use any delete operation)

and the request sent was therefore filled with :

[
  {
    targetId: undefined,
    targetType: undefined,
    key: undefined
  },
  {
    targetId: undefined,
    targetType: undefined,
    key: undefined
  }
]

which the ledger didn't know what to do with it

---

basically, our generator was at fault, the api works as expected (as already mentioned few months ago), but I failed to see this issue few months back sorry about this!

---

One thing I might ask is to have a better error in such case, as the unexpected error while forging log: not found was very cryptic and led me to wrong debugging paths.

But even then, this is definitely on us, thanks for taking the time to help me debug an issue that wasn't in your control at all, it was very appreciated and even reading this back it still is!