AWS File Uploader (NoGUI) not returning File URL?

[liz]

I deleted my post on this earlier because I thought I figured it out… but I haven’t. I’m having trouble getting the NoGUI version of this plugin to return the File URL. A couple of notes:

• I am using the GUI element of this plugin in the same environment, and the URL is returning fine.
• I tried returning AWS Name instead of URL ,and that worked fine. All the other values I’m using in the attached screenshot are also returning fine.
• I’m assigning it to a state here, but I also tried outputting FileUploadersNoGUI A’s URL directly, and there is no value.

Here’s what I’m using to return the URL… is there something I’m missing?

[egor.smorodinov]

Hello liz,

Thank you for reaching out and providing the details!

Based on the setup you shared, it seems like the issue might be related to the timing of when the URL is being retrieved. The URL might not be available immediately after starting the upload process, so you might need to ensure that you’re retrieving the URL after the file upload has completed successfully.

Here are a couple of things to check:

Confirm Workflow Order: Ensure that the URL is being fetched after the file upload is complete. You might want to move the action to set the state for the URL after the file has been successfully uploaded.
Add a short delay, and see if this helps.

Additionally, could you please provide the following to help us assist you further?

• Screenshots of your current plugin setup and configuration.
• A Loom recording or screenshots of the workflow in debug_mode=true, with the debugger set to step-by-step to check every value passed along the workflow.

Once we have these details, we’ll be able to assist you more effectively!

Best regards,
Egor Smorodinov,
Support Team
Browse all Zeroqode Plugins for bubble

[liz]

It’s the timing… I ended up moving the workflow elements that should occur after the file has been uploaded to a separate workflow that verifies the upload is 100%.

And just to add… this doesn’t seem to be 100% reliable (maybe the URL isn’t generated yet even if the state says it’s 100% uploaded?). I am also adding a pause before trying to capture the URL.

[egor.smorodinov]

Hi liz,

Thanks a lot for the update!

You’re absolutely right — when working with server-side operations like file uploads, timing can definitely play a role. The upload process may be marked as “complete” on the frontend, but in some cases, the server might still be finalizing the file storage or URL generation in the background.

This can be due to a variety of real-world factors like server load, network latency, or temporary CPU throttling. It’s not an excuse, just something we see occasionally, especially in larger or more complex apps where workflows get long or resource-intensive.

We think your approach of separating out the post-upload logic into its own workflow is a really smart and scalable workaround. Longer workflows tend to accumulate more execution time on Bubble’s backend, so isolating time-sensitive actions like retrieving the URL can definitely help with reliability.

Additionally, you might consider setting up a conditional check to ensure the URL is only fetched once the upload has fully completed. The plugin exposes a “Percent uploaded” value, which you can use to trigger follow-up actions only when it reaches 100. For example, you can configure your workflow to run the URL-fetching logic only when FileUploaderNoGUI's Percent uploaded is 100. This adds an extra layer of reliability and helps prevent premature attempts to retrieve the URL before it’s actually available.

Best regards,
Egor Smorodinov,
Support Team
Browse all Zeroqode Plugins for bubble