"Schedule API Workflow" Not Running & No Server Logs - Help Needed (OpenAI API + Whisper)

Hello Bubble community,

I’m at the final step of my app and have hit a wall with a backend workflow that won’t trigger. I’d be really grateful for any assistance.

Simply put:

  • The webapp is an English language proficiency test.
  • The test taker submits answers in the form of multiple choice, short/long answer and audio recording questions.
  • At the end of the test, the test taker presses a button to submit their final answers and see their results > then the Backend API Workflow (making use of OpenAI & Whisper) is prompted to instantly show the test results (including the written and spoken sections based on specific criteria provided in a prompt),

The Goal:

  1. User clicks a “Submit” button on the front-end (english_test page).

  2. This should trigger a backend workflow called masterGrader using the Schedule API Workflow action.

The Problem:
The masterGrader workflow never starts. I’ve waited several minutes and my Server Logs are completely empty for this workflow. The user is left on a permanent loading screen.

Here’s a screenshot of my Schedule API Workflow action:

What I’ve already checked:

  • In Settings > API, the Enable Workflow API and Backend Workflows box is CHECKED.

  • In the masterGrader backend workflow, the “Expose as public API workflow” box is CHECKED.

  • There are zero errors in my app’s issue checker related to this workflow.

It feels like the Schedule API Workflow action is failing silently without creating a log or an error. Has anyone seen this before? Is there a privacy rule or a setting I could be missing that would prevent a front-end workflow from scheduling a backend one?

Thank you for any help you can offer!

Hey,

The most obvious place is in the “search for answers” part of your workflow. If the search returns no answers then there won’t be anything to run. In the debugger do you see it return values? Also, worth noting - since yesterday afternoon I’ve been getting nothing in the logs tag at all in terms of back-end workflows. Bubble support have told me there’s an issue but I haven’t heard anything else.