Creating journaltransaction using background job seems very slow

[ErikW]

Hi,

We have posted a bunch of transactions more than an hour ago to the tenant: bc126541-7e7b-11ec-b60b-0638767d04b5.

The data has not yet arrived in the system. Is this as expected or is there an issue here? Seemed a lot more rapid yesterday. As example here is the state of one of the backgrounds jobs we have submitted:

{

    "id": "badf9493-1239-41ee-aa48-cc4b577cf7c7",

    "status": "Queued",

    "statusCode": 0,

    "receivedUtc": "2025-04-16T11:07:56.3568893Z",

    "webhookAddress": "https://f5ad-98-128-206-2.ngrok-free.app/api/CashTransactionCallbackSv/?Id=3b0430f7-1fc5-44c8-83f3-2...",

    "originalUri": "http://finance.visma.net:80/1044021001/api/v2/journaltransaction",

    "hasResponseContent": false,

    "hasRequestContent": true

}

[Oskar Jansson]

Hi, the problems should be fixed now. Please contact us if you have any more problems after April 26th.

Postmortem from the incident: “Our queueing service for background tasks was not working optimally and was not able to scale according to the load. We improved the mechanism so that scaling is more robust and will scale resources faster according to load.”

[LudwigWikblad]

Hi! Just confirming my newly won write-access here, and following this thread.

// Ludwig

[Oskar Jansson]

We are still having issues. Follow updates at https://status.visma.com/incidents/j97c01tdgg4chttps://status.visma.com/incidents/j97c01tdgg4c 

[Oskar Jansson]

Hi, the development team is working to find a solution to the issue, but the actions taken so far have not shown any improvements.Thank you for being patient. We will update you when we have more news.

[Oskar Jansson]

Hi @ErikW,

Please email api.consulting.se@visma.com with the details of your issues and include the application's clientId. We are currently investigating this and would like to gather information from your perspective as well.

[Rozhat]

Hi, 

Please take contact with our support regarding this : 

Norway & Denmark https://visma-swno.my.site.com/s/api or MAIL : cloud.api.support@visma.com
Sweden - E-MAIL : api.consulting.se@visma.com
Netherlands https://visma-software-nl.force.com/supportportal/s/ -
Finland - E-MAIL : api.consulting.se@visma.com

[MvcMartin]

Hi Rozhat,

We did last thursday - got ticket id 00325673. Still no reply.

Regards,

[Oskar Jansson]

Hi,

I am investigating this. I will respond to you via email.

[MvcMartin]

We are still experiencing this issue and after some investigation it looks like it's a problem with the background job's state not updating.

The status is stuck on Queued, however the transaction is released in Visma UI. Seems like we have to revert to checking on the entity periodically. GET /inventoryissue/XYZ -> status == Released?

[MvcMartin]

We are experiencing the same issue, with specifically /inventoryisse and /inventoryReceipt, the background tasks takes a long time to complete.

They take anywhere from 2 to 40 minutes at the moment.

Tenant: ce0a2c1c-54a4-11ea-973a-0ac295605980