Hi Botpress team. I’m building a Viber agent in a Free workspace to email a lead summary after a visitor consents. Its HTTP Request tool should POST JSON to Resend’s /emails endpoint with bearer authentication and Content-Type: application/json. In Preview, the agent invokes the tool, but the activity says 'Tool execution did not complete.' Botpress Logs say 'The agent runtime hit an internal error' about 20 ms after invocation. Resend shows no incoming request or API key activity. I reproduced this with a static, valid JSON body, so the failure does not appear to depend on generated lead content or template variables. The tool is enabled in the draft, and these changes have not been published. Should a Viber HTTP Request tool execute in Preview on the Free plan? Is there a supported way to determine why dispatch fails before the outbound request? I can share the runtime reference and tool ID privately with Botpress support.

Yes, Botpress Viber supports HTTP Request tools with bearer authentication, and Preview supports testing unpublished changes. However, the error occurring before Resend receives a request suggests a Botpress runtime or tool-dispatch issue, not necessarily a Resend configuration problem. I can help troubleshoot the tool configuration, isolate the runtime failure, and identify what evidence to provide Botpress support. @billowy-laptop-73112

Thanks. I checked Inspect > Logs for the failed Preview call. Tool http_vy3dnd failed in 20 ms on October 27 at 11:20:07 AM EDT. The concurrent internal-error references are 01M5YZ51063ASPW3R183GNN0W6 and 01M5YZ51066TDTJ68B9BRY941K. Preview shows a populated input but only “Tool execution did not complete”; Resend shows no corresponding request. Could you trace those references and tell us whether Botpress attempted the outbound HTTP request, and which step failed?

The two references point to an internal Botpress runtime error, but I can’t access Botpress’s internal traces to confirm whether the outbound request was attempted. The 20 ms failure and absence of a Resend request suggest the failure may have occurred before dispatch, but that isn’t conclusive. I can help you isolate the failure and review the HTTP Request configuration. Botpress support will need to trace both references to identify the exact failing step.

Thanks. Coukd you please trace the two error references I provided and confirm whether Botpress attempted the outbound HTTP request. The failure occurs in about 20 ms, and I see no corresponding request in Resend’s API logs. Id you can identify the exact failing step and let me know whether this is a runtime/tool-dispatch issue or a problem with my HTTP Request configuration. I can provide a redacted configuration and another test timestamp if needed.