Has anyone used a reasoning LLM model in their APIs?

Questions
15

The overall 5 minute limit. Understand that when generating a Bubble app with AI, you “ask” for 5-7 minutes. This is standard stuff in the current LLM landscape. This is a screenshot of Bubble’s own product.

Screenshot 2025-10-16 081347
Screenshot 2025-10-16 081347407×258 31.5 KB

Consider the following extremely common LLM use case.

You have 3 reasoning LLM calls (2-4 minutes) that you need to make that don’t depend on each other whatsoever, but that will converge into a single “Thing” down the line. There’s also an intermediate formatting call for each (a few seconds) before they get merged.

Under a sequential scenario they would easily fit into a single workflow.

         `┌─────────────────────────┐
         │  Bubble Workflow Starts  │
         └────────────┬────────────┘
                      │
       ┌──────────────┼──────────────┐
       │              │              │
┌──────▼──────┐ ┌────▼───────┐ ┌────▼───────┐
│ Reasoning A │ │ Reasoning B │ │ Reasoning C │
│  (2–4 min)  │ │  (2–4 min)  │ │  (2–4 min)  │
└──────┬──────┘ └────┬───────┘ └────┬───────┘
       │              │              │
┌──────▼──────┐ ┌────▼───────┐ ┌────▼───────┐
│ Format A'   │ │ Format B'   │ │ Format C'   │
│ (seconds)   │ │ (seconds)   │ │ (seconds)   │
└──────┬──────┘ └────┬───────┘ └────┬───────┘
       │              │              │
       └───────┬──────┴───────┬──────┘
               │              │
         ┌─────▼──────────────▼─────┐
         │ Merge / Assemble results  │
         │  → single Bubble “Thing”  │
         └─────────────┬────────────┘
                       │
                 ┌─────▼─────┐
                 │ Save Thing │
                 └───────────┘`

Under the current limitations where every LLM call must be handled sequentially, it no longer fits.

┌─────────────────────────┐
│ Bubble Workflow Starts │
└────────────┬────────────┘
│
┌───────▼────────┐
│ Reasoning A │ (2–4 min)
└───────┬────────┘
│
┌───────▼────────┐
│ Format A’ │ (seconds)
└───────┬────────┘
│
┌───────▼────────┐
│ Reasoning B │ (2–4 min)
└───────┬────────┘
│
┌───────▼────────┐
│ Format B’ │ (seconds)
└───────┬────────┘
│
┌───────▼────────┐
│ Reasoning C │ (2–4 min)
└───────┬────────┘
│
┌───────▼────────┐
│ Format C’ │ (seconds)
└───────┬────────┘
│
┌─────────▼────────────────┐
│ Merge/Assemble → 1 Thing │
└─────────┬────────────────┘
│
┌────▼─────┐
│ Save Thing│
└──────────┘

So really there are two problems here.

  1. The extremely strict workflow timeout.
  2. More importantly, the lack of being able to specify parallel/sequential in backend workflow actions.

Thank you @tj-bubble , really appreciate you!!