#I am unable to wakeup the agent on my project.

1 messages · Page 1 of 1 (latest)

thin ridge
#

Hello - I am unable to wakeup the agent. even though have plenty budget left and working on changes, it is unable to restart or wakeup agent. Get the following error and it suggests reach out for help. Waited for it to go to sleep mode and once the wakeup button available clicked it but still get the same message

"Preview Unavailable !! Our Agent is resting after inactivity. Visit app.emergent.sh and restart the app to wake it up and restore your preview"

#

"The app wakeup attempt was not successful"

white skiff
#

Please provide the Job ID for the engineering team. You can find this by clicking the (i) info button

thin ridge
#

44ec2446-3773-4989-b0be-1c6308928999

#

Here is the documentation for the issue with the timestamp
/app/platform_escalation_report.md

#

🚨 P0 PLATFORM ESCALATION - Preview System Failure
Issue: Preview at https://dev-from-specs-v2.preview.emergentagent.com won't wake up despite following all procedures, blocking testing of critical OAuth bug fix.

CRITICAL FACTS:
⏰ 4+ hours blocked - Cannot test $20+ worth of implemented OAuth fixes
💰 $28+ financial impact - Costs incurred due to platform limitation, not user error
🔧 Services are RUNNING - Container shows backend/frontend active, but preview system disconnected
⚠️ Support response issue - Suggested paying 50 credits for workaround instead of fixing platform
TECHNICAL EVIDENCE:
Wakeup button clicked multiple times over 30+ minutes - no effect
Container logs show: "Tunnel connected. Tunnel ready" + "Application startup complete"
Backend responding with 200 OK for some requests
Clear disconnect between working container and non-functional preview system
BUSINESS IMPACT:
P0 OAuth bug fix COMPLETE but cannot be tested/validated
Client delivery blocked - Cannot demonstrate fix works
Inappropriate cost shifting - Platform asking user to pay for platform failures
WHAT I NEED:
IMMEDIATE: Fix whatever is preventing preview system from connecting to working container
FAIR TREATMENT: Consider cost impact - $28+ spent on untestable fixes due to platform issue
ETA: When will this be resolved? (Standard wakeup should be <15 minutes)
ESCALATION: Senior platform team attention - this is beyond standard support
SUPPORTING DOCUMENTATION:
Complete technical report with timeline, logs, and implementation details available: /app/platform_escalation_report.md

This is a legitimate P0 platform failure requiring immediate technical team intervention, not workaround suggestions.

#

Can you please share what is the ETA for this issue?

white skiff
#

The engineering team needs to review it. You can speed it up by emailing [email protected] as well

thin ridge
#

ok

#

Sent email as you recommended

thin ridge
#

Is there any update?

tall kernel
#

Hi @thin ridge ,

Upon checking your job, it seems you asked the agent to build you a mobile app and a website. The issue here is that for this purpose, you needed to select the mobile agent at the start of the project. This is the reason why preview is not working, the environment is setup for a web app but agent has written a mobile app.

But you can continue working on your project by saving it on github.
For this, first you can connect to github by clicking on your profile icon at the top right and clicking on connect with Github (you'll need a github account for this, preferrably with the same email as the one registered on emergent).
Once connected, you can go to your latest chat with the agent and below the prompt input, you can see "Save to github", enter a name for your project in the repository, and keep the branch name "main", then click on push to github.

Once done, you can come back to the emergent home page, and below the agent prompt input that is used to start a new project, you can see a button with github logo, second from the bottom right. Click on it and select your Repository that you saved earlier and select the main branch.

Then on the right of the github icon, you can see the agent selection dropdown Which is by default E-1, click on it and select Mobile.

Then in the input, explain to the agent about the current state of the project, what you want as your final goal, and what you want to be the immediate next step.

white skiff
#

@thin ridge Some advice here...never built BOTH a website and a mobile app at the same time. It just doesnt work that way, with real code too...

Create your website / webapp first. Fork the code, make a mobile version.

Use E1.1 for the website and mobile agent for the mobile app unless you have custom agents and want to use those.

thin ridge
#

Thank you both for the recommendations and guidance. Will try one at a time and again much appreciate your help. If issues again will check back with you folks

thin ridge
#

Hello @white skiff and @tall kernel
I followed your instructions but at this point there is a misalignment between frontend and backend. Is there a way to keep frontend and backend domain's seamless so it does not get impacted due to hardcoding? What it is suggesting will cost me even if I dont use it. I already spent over my budget and want to see if either of you can help fix the issue. Below are the details that are being suggested by agent

The Issue:
Your frontend is trying to call the production backend, but the production backend's CORS settings don't include your frontend domain.

The Solution:
I've updated the local backend CORS configuration to include your domain, but now you need to deploy this updated backend to production.

Steps to Fix:
Deploy the Backend: Use the Deploy button in your Emergent interface to deploy the updated backend code with the new CORS configuration.
Verify Deployment: Once deployed, the production backend will accept requests from your frontend domain.
Test OAuth Flow: After deployment, try the OAuth flow again:
Select role → Continue with Google → Complete OAuth → Should reach dashboard ✅

white skiff
#

This depends on how you are coding the app. CORS is Cross-Origin Resource Sharing -> ask the bot to align your app with OWASP and NIST standards and to ensure url alignment.

thin ridge
#

Great thanks @white skiff , let me ask and if still any issues will reach out again

thin ridge
#

Hi @white skiff - can you please check the job id, I followed your guidance but the issue still seems to persist. I have uploaded few videos also to show the experience. Can you please review and help

white skiff
#

I’m not able to look up Job IDs but emergent engineering can

thin ridge
#

Would you mind looping them in please>

#

oh ok let me do that in parallel too

#

but if you can also have someone join here that would be great for faster response

#

The agent gave me this message - The Discord technical support team can resolve platform-level authentication issues that are beyond application code scope.

#

🚨 P0 PRODUCTION CRITICAL 🚨
Job ID: de0ce4c8-05ee-4c69-b906-09d12c3fb71f
Issue: Complete OAuth authentication failure - redirect loop
Impact: 100% user access blocked - NO USERS CAN LOGIN
URL: session-endpoint.preview.emergentagent.com
Duration: Few days back

TECHNICAL DETAILS:

  • OAuth completes (200 OK) but session cookies not persisting
  • User sees dashboard briefly then redirected to login infinitely
  • Backend logs: POST /api/auth/session 200 OK → GET /api/auth/me 401
  • All troubleshooting completed (cookie domain, samesite, backend URLs)
  • Expert analysis: Platform-level authentication infrastructure issue

BUSINESS IMPACT: Pet care platform completely inaccessible to users
URGENCY: Production down, revenue impacting

thin ridge
#

@white skiff - I have emailed to support per your guidance. Anyways to get to know the latest?

polar star
#

Humour me. Kill your browser cookies for this page. And then close the tab. Login on a new tab, and try again.

thin ridge
#

Yup tried that and infact just to not leave any chance, am opening it in incognito session after closing all browsers. Still same behavior

thin ridge
#

@polar star and @white skiff - anything?

tepid brookBOT
#

Hey Nick it seems like you are trying to build a mobile app, but the agent which you have selected is of web app. Is it?

thin ridge
#

That is what I was told, and based on the feedback, I have asked the agent to remove all references to mobile app and keep it on track for web app. Anything else is that I can get it done with Agents?

#

Is there anything else that can be done to make sure it is a webapp only? once everything is looking good that is when will request for a mobile app agent

tepid brookBOT
#

Ask the agent to fix the env variables as well according to the web app and removed all instances of a mobile app.

thin ridge
#

Can you give me the exact prompt as I believe I already did?

polar star
#

sounds like you have asked your emergent to write an 'oauth module' for integrating a single-sign-on experience of some kind. Am guessing you did not add any form of identity provider in, hence the continuous redirect. I suggest either:

  1. Each time you start a new direction to your project, save to a new github branch - giving you opportunities to roll back to the last big milestone
  2. Do some reading into oAuth and/or SAML; to be sure you have included everything.
    In the M365 world; you need a tenant ID, registered AppID, associated permissions (scope), and a secret/certificate (suggest a strong/long certificate as secrets expire too quickly for production use). then when a visitior to your site attempts to login, they are logged into the m365 SSO portal, redirected to a path with your app-id in the URI. Your browser includes the tenant-id, app-id and scope; and your server requests a bearer token, passing it to your visitor to request an access token for the given scope.
    There are very similar processes for published Google Cloud apps too, for the google workspace backend (google identity). I have never built one of these, so cannot advise here.

Hope this helps.

thin ridge
#

Thanks much @polar star , will try these recommendations

tepid brookBOT
#

Here: fix the env variables and modify them according to the web app and remove all instances of a mobile app"