Workflows with "Send http Request" stopped working after upgrade to 3.13.2

[TMAG_mbohlender]

Hi Yuri,

as a first step I performed a full docker upgrade with

$ docker compose pull && docker compose up -d

but that changed nothing. I however noticed that I have overseen two additional log lines yesterday that are logged BEFORE those posted yesterday and these two lines contain the workflow ID. So the full set of log lines ist as follows:

[2026-07-08 05:45:06] ERROR: (0) Workflow 6999aca914463b641: Action failed, sendRequest 0, Workflow: Send Request action: 0 response..
[object] (Espo\Modules\Advanced\Core\Workflow\Exceptions\Se ndRequestError(code: 0): Workflow: Send Request action: 0 response. at /var/www/html/custom/Espo/Modules/Advanced/Core/Workflow/Actions/SendRequest.php:451)
[2026-07-08 05:45:06] ERROR: (500) Workflow action failed. Workflow: Send Request action: 0 response. :: POST /WorkflowManual/action/run
[object] (Espo\Core\Exceptions\Error(code: 500): Workflow action failed. at /var/www/html/custom/Espo/Modules/Advanced/Core/Workflow/ActionManager.php:114)
[previous exception] [object] (Espo\Modules\Advanced\Core\Workflow\Exceptions\Se ndRequestError(code: 0): Workflow: Send Request action: 0 response. at /var/www/html/custom/Espo/Modules/Advanced/Core/Workflow/Actions/SendRequest.php:451)

After applying the fix version 10.0.1 everything is working fine again. So I assume that this was also an IPv6 related issue caused by the "Send http request" action INSIDE the workflow as all other workflows that contain only "normal" data operations and steps have been working fine all the time

Great job in providing a fix that quickly, thank you for the excellent support

Regards
Michael

[TMAG_mbohlender]

I will schedule maintenance in the late afternoon and report back with the results. Thanks for the quick reply so far

[yuri]

It's better to do a proper migration if you use our docker setup: https://docs.espocrm.com/administrat...-to-espocrm-10. Though it's not related to your problem.

It could be because of the docker container having not enabled IPv6. There's a chance that v10.0.1 will solve this problem. Check this thread, might be related: https://forum.espocrm.com/forum/inst...bhook-failures.

[TMAG_mbohlender]

I think this: Installation with Docker - EspoCRM Documentation is the solution? And there especially the "Upgrade" and "Troubleshooting" Sections

[TMAG_mbohlender]

Hi Yuri,

yes I do and I did NOT update the containers but used the built-in update functions for Espo (on the CLI) and the extensions (via WebUI). I assume I need to do a full update of the containers, right?

EDIT: the original install was via the script. I remember that for this install type there are special commands for upgrading but just can't find them in the docu. Can you point me to the right entry point there?

[yuri]

Hi Michael,

Do you use a Docker setup?

[TMAG_mbohlender]

Hello to the community,

I hope somebody can help with this: I updated Espo and all my extensions yesterday as usual. AdvancedPack was updated from 3.13.0 to 3.13.2, EspoCRM itself from the last 9.x version to 10.0. Since then both of my two manual workflows which send an http request to MS Power Automate stopped working. When starting them I receive lines like this in the log:

[2026-07-07 06:55:49] ERROR: (500) Workflow action failed. Workflow: Send Request action: 0 response. :: POST /WorkflowManual/action/run
[object] (Espo\Core\Exceptions\Error(code: 500): Workflow action failed. at /var/www/html/custom/Espo/Modules/Advanced/Core/Workflow/ActionManager.php:114)
[previous exception] [object] (Espo\Modules\Advanced\Core\Workflow\Exceptions\SendRequestError(code: 0): Workflow: Send Request action: 0 response. at /var/www/html/custom/Espo/Modules/Advanced/Core/Workflow/Actions/SendRequest.php:451)

The workflow action is triggered and logged in the detail view of the workflow but I immediately see the "Internal Error" message popup in the top middle of my browser window and NO incoming request is logged in Power Automate.

I am confused about the first line of this log as it seems that in the logging action in ActionManager.php the workflowId is not visible in the log line.

Does anybody has any idea where to look at and / or what further details do you need?

Regards
Michael