automa icon indicating copy to clipboard operation
automa copied to clipboard

1.29.8 Workflow Stuck at Parameter Prompt After Submitting Parameter Values

Open codecrafter97 opened this issue 11 months ago • 17 comments

Describe the bug After users input parameter values and click the "Submit" button, the workflow fails to progress to the next block.

To Reproduce Steps to reproduce the behavior:

  1. Trigger workflow https://www.automa.site/workflow/fsjfz_HmxyOJBnCkvrxb5
  2. Enter parameter input
  3. Click submit button
  4. Not responding, does not proceed to next block

Expected behavior Proceed to next block

Screenshots From log, it is stuck at Parameter prompt Image

Desktop (please complete the following information):

  • OS: Windows
  • Browser: Microsoft Edge
  • Extension Version: 1.29.8

Additional context This issue began occurring today, and the workflow was functioning correctly yesterday. Downloaded 1.29.6 version from here https://www.crx4chrome.com/crx/261936/, rename .crx to .zip, load unpacked, the workflow working again

codecrafter97 avatar Mar 11 '25 03:03 codecrafter97

Are there any specific value requirements for the parameters to be filled in?

After attempting to install and run the program, I entered "1" and was redirected to https://page-blank.vercel.app/.

It appears to be functioning as expected.

bingren-yd avatar Mar 11 '25 09:03 bingren-yd

Attached is the recording.

I have reinstalled Automa v1.29.8.

The first workflow trigger worked correctly.

However, subsequent workflow triggers get stuck at the parameter prompt.

https://github.com/user-attachments/assets/b09e4099-c4c1-41b4-a123-1d8a75e69735

Only the first workflow able to proceed to the JavaScript code block

Image

codecrafter97 avatar Mar 11 '25 14:03 codecrafter97

yeah, i am the same problem.

zhongqingsong avatar Mar 27 '25 08:03 zhongqingsong

+1

nbvnbv avatar Apr 02 '25 15:04 nbvnbv

I have the same issue on v1.29.9, parameter prompt stucks.

nightrider77 avatar Apr 11 '25 10:04 nightrider77

Same issue here. I fill in the prompt but it doesn't move on to the next step. I'm not sure how to get around it.

Image

3Deyedoc avatar Apr 11 '25 21:04 3Deyedoc

@bingren-yd Mister, when is this issue expected to be resolved? Thank you.

nightrider77 avatar Apr 11 '25 21:04 nightrider77

@bingren-yd I'm curious too. I can't find a good work around. The parameter prompt will work on occasion. When it does it's only the first prompt the first time after rebooting my computer.

3Deyedoc avatar Apr 15 '25 03:04 3Deyedoc

Same issue here, however it seems to only happen on Chromium based browsers (tested Chrome, Edge, Vivaldi, Opera). Anything Firefox based works fine (tested Firefox, Zen, LibreWolf, Waterfox, Floorp).

yourlocalmudpuppy avatar May 02 '25 18:05 yourlocalmudpuppy

I saw the update but still getting the same issue. It will work the first time but everytime after the parameter prompt doesn't move forward.

Image

3Deyedoc avatar Jun 03 '25 17:06 3Deyedoc

I also encountered, version: 1.29.10

SimFG avatar Jun 16 '25 09:06 SimFG

In addition, it seems that it is impossible to get the parameters in the prompt, such as {{ variables.keyword }}

SimFG avatar Jun 16 '25 09:06 SimFG

https://github.com/SimFG/automa/commit/24172254ad1bd6d0bdad7b7770a62028fcb56079 I tried to fix it with cursor, but I am not familiar with the front end. I have tried the case I used and the problem should have been solved.

SimFG avatar Jun 16 '25 12:06 SimFG

I have the same issue on v1.29.10, parameter prompt stucks.

qq-admin avatar Jun 30 '25 03:06 qq-admin

Same problem - works only once and then stops working. Variables are empty after 1st run.

expanous avatar Jul 07 '25 10:07 expanous

The parameter block is a crucial feature in browser automation tools, particularly in Automa. Unfortunately, I've discovered that it only functions correctly when included in trigger blocks. If you add the parameters block anywhere else within the workflow, it fails to work properly. Despite multiple updates since this issue was first noticed, the problem persists. We hope the @bingren-yd can address and resolve this technical limitation soon.

iMoeenD avatar Aug 19 '25 17:08 iMoeenD

Still waiting on a solution for this bug. I hope there's been progress.

3Deyedoc avatar Oct 15 '25 21:10 3Deyedoc