Unable to send Slack block messages

[IDarma]

I've been trying to send a block message from the SlackBlockBuilder automation. However, when I try to test it out via the debugger panel, it would result in an error.

Spoiler

Command: 

!SlackBlockBuilder list_name="SLACKV3_BLOCK_ASK_URLALERT" channel_id="[redacted]" persistent="false" reply="Thank you for your response." lifetime="1 day" defaultResponse="NoResponse" slackInstance="SlackV3_instance_test"

Reason

Error from Scripts is : Script failed to run: Timeout Error: Docker code script failed due to timeout, consider changing timeout value for this automation, Error: write |1: file already closed (2604) (2603)

Similar error happens with SlackV3's send-notification command when you use its blocks parameter:

Spoiler

Command: 

!send-notification message="This is a test (send-notification command)" channel_id="[redacted]" ignoreAddURL="false" blocks="{ \"blocks\": [ { \"type\": \"header\",

Reason

Error from SlackV3 is : Script failed to run: Timeout Error: Docker code script failed due to timeout, consider changing timeout value for this automation, Error: Failed to decode (loop) data from docker code script: unexpected EOF This may happen when you don't return an explicit entry (or entries) from a script. for entry structure please review the 'Script Helper' (2605) (2604) (2603)

The command works fine without the block parameter, though:

Spoiler

Command: 

!send-notification message="This is a test (send-notification command)" channel_id="[redacted]" ignoreAddURL="false"(SlackV3)

Message sent to Slack successfully. Thread ID is: [redacted]

For what it's worth, I tried debugging this on my VM and inspected the instance's log there. It said something along the lines of "cached context has expired." Screenshot of the log is attached.

Could anyone assist me with this issue? Thanks!
Cortex XSOAR 

[gyldz · Accepted solution]

If you want to send a Slack block, you need to create an incident rather than test on a debugger, just due to how the entitlements are handled in the playbook debugger.  This is a known limitation.

[KHassan]

Hi @gyldz ,

So, how do I create an incident so that Slack Block gets sent to the Slack channel?

[IDarma]

Yeah, I discovered shortly after creating this thread that you must test this on an existing incident rather than using the debugger panel. They didn't really make this clear in the documentation. Ended up wasting hours trying to find the cause. 😕

@KHassan, you can test it on any kind of incident. Just create a playbook with the SlackBlockBuilder task in it, then open an incident and change the playbook in the Work Plan tab.