A subflow that we use regularly started failing today. It shows an error message:
“Run failed for an unknown reason, contact support. - ,” And the run log won’t load any input or output data for any of the steps.
It keeps re-queueing itself every minute and failing with the same error message.
The calling flow is stuck in a paused state at the step that calls this subflow.
Subflow url: Activepieces
This subflow is now re-queueing itself about 40 times per minute, failing with the same unknown reason every time.
Hi @hanley
I escalated it to the team, they will take look soon.
Any updates? The sub-flow is constantly re-queuing itself and failing, and has been for about 24 hours now.
Can you email us the parent and subflow to [email protected], that would help us fix it faster
I’ve emailed them the relevant flow and sub-flow URLs. Thanks.
Hi @Hanly,
I just talked to the team. It’s a flow they have been investigating for over 24 hours!
It seems the library used in the code piece needs the HOME environment variable, and that was a regression in our sandbox environment.
The team will publish a fix in 1–2 hours.
Thanks,
Mo.
It should be fixed @hanley The team confirm that the runs are no longer have internal error state
Works great. Thanks!
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.