Reference
Troubleshooting
Something looks wrong? Here are the most common confusing states and how to get past them.
I deployed an app but it's not in floom status
Why this happens
Your CLI is probably signed in under a different Floom account than when you deployed. Apps are tied to the account that deployed them, not to your machine — so if you've ever logged out and back in, or used a different email, those apps won't show up.
How to resolve
floom auth whoamiThis shows which email your CLI session is using right now.
If the email is wrong, run floom auth logout then floom auth login and sign in with the original email. Your apps will reappear. If you're not sure which account deployed the app, look at the app's URL — the 8-character suffix (e.g. myapp-f7392ddf) matches the user ID of the account that created it.
My run hangs for 30+ seconds before output appears
Why this happens
Floom v0.4 uses a single shared sandbox tier. When multiple runs arrive at once, they queue and execute one at a time. The queue is deliberate — it keeps runs from stepping on each other. Your run will complete; it's just waiting for the ones ahead of it to finish.
Normal wait under typical load: under 5 seconds. Under heavy load: up to 5 minutes, after which the run is marked failed. Nothing to fix — this is working as designed. Parallel execution is planned for v0.5.
Connecting Gmail or Slack shows 'Composio' on the consent screen
Why this happens
When you click "Connect Gmail" on /connections, you'll see a Google sign-in screen that says "Composio wants access to your Google Account". This is expected. Floom uses Composio to handle OAuth for integrations — Composio is the registered app with Google, Slack, and other providers, so its name appears on the consent screen. Once you connect, Floom uses your credentials to call those services on your behalf.
Not a bug. Floom is working toward direct OAuth registration with Gmail, Slack, and GitHub for v0.5 — those consent screens will show "Floom" instead of "Composio".
I lost my run output when I refreshed the page
Why this happens
If you ran the app without signing in, your result is tied to a one-time view token that Floom stores in your browser's local storage. Clear your browsing data, switch to a different browser, use incognito mode, or open the page on another device — and the token is gone. Without the token, there's no way to get the result back.
To keep your runs permanently, sign in before running. Signed-in users have full run history at any time, from any browser. For anonymous runs, copy the output before navigating away.