# Longer transactions don't get signed **URL:** \ **Category:** Support\ **Created:** [March 12, 2024, 11:37am UTC](https://community.fireblocks.com/t/longer-transactions-dont-get-signed/794 "2024-03-12T11:37:08Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![andrew](https://avatars.discourse-cdn.com/v4/letter/a/f19dbf/32.png) [@andrew](https://community.fireblocks.com/u/andrew)\ **Post date:** [March 12, 2024, 11:37am UTC](https://community.fireblocks.com/t/longer-transactions-dont-get-signed/794/1 "2024-03-12T11:37:08Z")
Hello, it appears that longer transactions don’t get signed by the Fireblocks. In the following code: ```auto const transaction = await this.client.createTransaction({ operation: TransactionOperation.RAW, source: {type: PeerType.VAULT_ACCOUNT, id: '0'}, assetId: 'HBAR_TEST', extraParameters: {rawMessageData: {messages: [{content: message}]}} }); ``` when `message` value is ` {"test": "test"}` the request returns correctly signed data: ![Screenshot 2024-03-12 at 11.29.47](https://us1.discourse-cdn.com/flex015/uploads/fireblocks/original/1X/56de56f0db07ee6d6d65bdd922c70c7e9161b690.png) When we use realistic value (with a different size) such as: `{"id":"85202d35-ecfa-4a2a-988b-83db7de96a77","status":"ISSUE","type":"Topic","action":"create-topic","lang":"en-US","name":"SCHEMA_TOPIC","description":"SCHEMA_TOPIC","owner":"did:hedera:testnet:E2pCYYGiXR3rSEMtc95xr2YNP3P2jyTyM4GXpsN836LR_0.0.3691957","messageType":"SCHEMA_TOPIC","childId":null,"rationale":null}` it does not sign the message and returns no error (see next post) ---
**Author:** ![andrew](https://avatars.discourse-cdn.com/v4/letter/a/f19dbf/32.png) [@andrew](https://community.fireblocks.com/u/andrew)\ **Post date:** [March 12, 2024, 11:37am UTC](https://community.fireblocks.com/t/longer-transactions-dont-get-signed/794/2 "2024-03-12T11:37:42Z")
![image](https://us1.discourse-cdn.com/flex015/uploads/fireblocks/original/1X/add8a970a3a5299eb2b7c3727b27aae9755b9a58.png) ---
**Author:** ![andrew](https://avatars.discourse-cdn.com/v4/letter/a/f19dbf/32.png) [@andrew](https://community.fireblocks.com/u/andrew)\ **Post date:** [March 19, 2024, 5:51pm UTC](https://community.fireblocks.com/t/longer-transactions-dont-get-signed/794/3 "2024-03-19T17:51:00Z")
@mnamakwala Appologies for tagging you directly, but my request has had no response for a week. Is there any chance you can verify this for us please? ---
**Author:** ![mnamakwala](https://avatars.discourse-cdn.com/v4/letter/m/b5a626/32.png) [@mnamakwala](https://community.fireblocks.com/u/mnamakwala)\ **Post date:** [March 21, 2024, 5:44pm UTC](https://community.fireblocks.com/t/longer-transactions-dont-get-signed/794/4 "2024-03-21T17:44:34Z")
Hey Andrew, I will take a look into this for you. Can you please provide a tx id for these two RAW transactions? ---
**Author:** ![andrew](https://avatars.discourse-cdn.com/v4/letter/a/f19dbf/32.png) [@andrew](https://community.fireblocks.com/u/andrew)\ **Post date:** [March 25, 2024, 9:25am UTC](https://community.fireblocks.com/t/longer-transactions-dont-get-signed/794/5 "2024-03-25T09:25:58Z")
Hi @mnamakwala, I hope you had a good week-end. Just reaching out to see if there’s been any progress on this? ---
**Author:** ![mnamakwala](https://avatars.discourse-cdn.com/v4/letter/m/b5a626/32.png) [@mnamakwala](https://community.fireblocks.com/u/mnamakwala)\ **Post date:** [March 25, 2024, 8:33pm UTC](https://community.fireblocks.com/t/longer-transactions-dont-get-signed/794/6 "2024-03-25T20:33:46Z")
Hey Andrew, Can you please provide some examples of failed transaction IDs? So I can investigate. We do have a limit too. You can aggregate a maximum of 127 messages for Raw Signing. > **[Raw Message Signing](https://developers.fireblocks.com/docs/raw-message-signing#:~:text=%F0%9F%93%98-,About%20messages,-Each%20message%20should)** > > ❗️WarningRaw Signing is a premium feature and not available in production workspaces by default. If you're interested in this feature and want to see if your use case is eligible for it, please contact your Account Manager to discuss it.However,... ---
**Author:** ![andrew](https://avatars.discourse-cdn.com/v4/letter/a/f19dbf/32.png) [@andrew](https://community.fireblocks.com/u/andrew)\ **Post date:** [March 26, 2024, 5:24pm UTC](https://community.fireblocks.com/t/longer-transactions-dont-get-signed/794/7 "2024-03-26T17:24:18Z")
Hi @mnamakwala , thank you - I will get you the transaction ID tomorrow. Just a note, we only send a single message so we don’t exceed the 127 threshold at all. ---
**Author:** ![mnamakwala](https://avatars.discourse-cdn.com/v4/letter/m/b5a626/32.png) [@mnamakwala](https://community.fireblocks.com/u/mnamakwala)\ **Post date:** [March 26, 2024, 6:38pm UTC](https://community.fireblocks.com/t/longer-transactions-dont-get-signed/794/8 "2024-03-26T18:38:58Z")
Yes please send in a transaction id, and I will check it. Thanks. ---
**Author:** ![andrew](https://avatars.discourse-cdn.com/v4/letter/a/f19dbf/32.png) [@andrew](https://community.fireblocks.com/u/andrew)\ **Post date:** [March 27, 2024, 11:03am UTC](https://community.fireblocks.com/t/longer-transactions-dont-get-signed/794/9 "2024-03-27T11:03:14Z")
The transaction ID was: dbe61c38-b485-4a11-aceb-96e7beb7018b. Hopefully you can help us! @mnamakwala ---
**Author:** ![mnamakwala](https://avatars.discourse-cdn.com/v4/letter/m/b5a626/32.png) [@mnamakwala](https://community.fireblocks.com/u/mnamakwala)\ **Post date:** [March 28, 2024, 12:03am UTC](https://community.fireblocks.com/t/longer-transactions-dont-get-signed/794/10 "2024-03-28T00:03:42Z")
Hi Andrew, I can see that tx dbe61c38-b485-4a11-aceb-96e7beb7018b was signed and the signature was sent. You should be able to find the signature in messages in the field “fullsig” Thanks ---
**Author:** ![andrew](https://avatars.discourse-cdn.com/v4/letter/a/f19dbf/32.png) [@andrew](https://community.fireblocks.com/u/andrew)\ **Post date:** [March 28, 2024, 10:03am UTC](https://community.fireblocks.com/t/longer-transactions-dont-get-signed/794/11 "2024-03-28T10:03:21Z")
> [@mnamakwala](#): > > was signed and the signature was sent. Hello @mnamakwala, thank you for your answer - we checked and indeed the result for the above-mentioned tx is available now. However it was not available then - in the immediate response which was confusing. We have now experimented with other variants of the same and determined that API seems to provide ‘answers’ with a delay - e.g. in each case we needed to poll for the answer and eventually the result came back. In our tests with small payloads we’ve seen such delays of around 8 seconds (we polled multiple times with 2 secs intervals) - is this expected? Is this what we supposed to do - i.e. we should keep polling until the result come back? Is there a webhook or other similar facility we can use instead of polling? ---
**Author:** ![mnamakwala](https://avatars.discourse-cdn.com/v4/letter/m/b5a626/32.png) [@mnamakwala](https://community.fireblocks.com/u/mnamakwala)\ **Post date:** [March 28, 2024, 6:51pm UTC](https://community.fireblocks.com/t/longer-transactions-dont-get-signed/794/12 "2024-03-28T18:51:02Z")
Yes, we do have a webhook feature. Please check out the article below about it. > **[Webhooks & Notifications](https://developers.fireblocks.com/docs/webhooks-notifications)** > > OverviewWebhooks allow you to get notifications for events that happen on your Fireblocks workspace such as: Incoming/outgoing transactionsTransactions status updatesNewly added Vault account, Contract wallet, Internal wallet, or External wallet. You... The payload size does not matter and should not affect the time required to sign a message. If there is more than one message. It might take more time.