Backend workflow not triggering in Live

Hey everyone! Yesterday, I pushed my application live! I was super excited; however, I noticed a backend workflow I’d created to run once per day isn’t triggering in live mode (it worked fine in dev).

My application is a content curation site that chooses three random articles each day from my database of articles, makes a new list with these three articles, and displays the list in a repeating group.

In dev, the backend workflow is triggered when I press a button. Pressing the button creates a new list and then schedules a recurring event (which creates a new list each morning). When I run this in dev, it works perfectly. However, once I pushed it live, pressing the button doesn’t seem to trigger the workflow. No new list has been created, and no recurring events have been scheduled in my log.

My plan was to press the button once in live, and then once the recurring event was scheduled, update the app so that the button isn’t visible. Is there a better way to trigger this event? Is there something I’m missing between dev workflows and live workflows?

The application is here, and the button is the big red block at the very bottom.

Can confirm the button is doing nothing in the network tab :slight_smile:

Could you share a screenshot of the workflow setup?

@ed19 I think I’m dumb… I’m not sure where the network tab is.

Upon further digging, I think the issue may be in my parameters. These are the parameters I have set up currently.

I think changing it to “detect request data” may help, but it brings up these two errors.

Screenshot 2024-07-19 at 8.01.34 PM

I’ve tried adding “Get data from page URL” but the expression isn’t accepted, and I’m confused about the operators it gives me.
Screenshot 2024-07-19 at 8.03.01 PM

You don’t necessarily need to have parameters if each action step is able to function without additional external data. Params are used to feed information into your api call where necessary, so not vital by any means.

Detect request data is used almost exclusively for receiving webhooks (or other external calls), so likely not what you need in this case either, since you just want to recursively generate a random list of articles. Use this option when you want the parameters to be defined by another source (or if you’re a hack like me use it to quickly generate complex data structures via the API connector :slight_smile: ).

Get data from page url is used to extract url parameters, so more of a front end option. They are defined using a question mark after the url for the first parameter, then ampersands for additional params.
e.g. https://test.com?article=my_article_name&author=author_name

With the above url, if you chose to extract “article” from the page url, it would resolve to “my_article_name”. If you extracted “author” it would resolved to “author_name”.

None of the above options should have any bearing on your setup I don’t think, so likely there’s some other issue stopping the call from happening at all. Have a look at the button’s work flow on the page, as nothing happens at all when I click it (even in web inspector).

2 Likes

@ed19 That was incredibly helpful, thank you so much for taking the time to explain.

The button is a single-step workflow, with the following settings.

Screenshot 2024-07-20 at 6.05.04 PM
Screenshot 2024-07-20 at 6.05.10 PM

I initially thought it might be a privacy setting issue, but everything is public, so it should be able to trigger by anyone pressing it (I believe).

Screenshot 2024-07-20 at 6.08.08 PM

Do you have any other ideas on how I might trigger the workflow? I feel like there’s a simple solution somewhere that I’m missing.

@ed19 Lol, I can’t believe how dumb I was. The workflow in the screenshots was on the wrong button. We’re now up and running. Seriously, thank you so much for taking the time to respond and help out.

Haha, I thought it might be something like that. It happens, glad it’s sorted :laughing: