Have you created any new conversations after the update? If so, please check the logs to see if any errors are still occurring, or confirm whether the fetching code is executing successfully.

You can share the conversation link—we’ll review the logs..

https://chatbot.yourgpt.ai/dashboard/adb20105-08cb-40a9-93f3-66b378b9a32a/debug?tab=logger&conversationId=17749372758257820

Here's the new conversation, I see in the logs that we are getting a response but not shown to the customer.

hello @sanskriti Where are you getting this process.env from? I don’t think it will work in this context.

what do you suggest we do? I have tried with hardcoded creds and using FLOW.SHOPIFY_CLIENT_ID and so on; both process lead to no response from the bot.

When you’re working on this in studio, please make sure to test it using the emulator and also check the logs.

Also, if you’ve added any config variables, make sure you’re actually using them correctly. If needed, you can print the variables or use the variable inspector/popup to verify what values are stored in them.

Your flow in WhatsApp is stopping because an error is occurring, and in some cases, it isn’t handled properly since no path is attached to manage it.

Hi @Sahil , We have tested with both emulator and live from whatsapp. We have used both our custom flows and templates from shopify given in your app. This is the standard Order Status flow template provided by your app for shopify order status, and I have it enabled in quick replies now instead of our personalised created flow, as you can see the templates are as it is, and none of the code blocks have been changed and config variables are set up as you mentioned, however the issue still persists.

Hi @Sahil @Rohit Joshi, we are using buttons in our whatsapp flow and we had a conversation with Rohit regarding the same that once the user has used a button it should be freezed however currently the butttons are always open and answers whenever they are clicked upon; even after using it once; even after the chat history is days old. After one use can the button be freezed?

hello @sanskriti The buttons shown in WhatsApp are controlled by WhatsApp itself. As far as we know, WhatsApp does not provide an option to disable buttons.

If you’ve come across any chats in whatsapp where buttons appear disabled, please let us know—we’ll look into it and check if there’s any supported way to achieve this.

Additionally, for older conversations that remain inactive for a long time, we offer an auto-close and auto-resolve feature. This resets the session after inactivity, ensuring that any new message is treated as a fresh session.

@Sahil @Himanshu Alternatively, could we make the irrelevant options disappear or turn invalid once the relevant one is selected? Basically, I’m wondering if there’s any alternative approach we can use here in case freezing isn’t possible right now.

@Sahil Hi Sahil, we keep encountering some issues with the base integration, our api status shows http 200 and status as successful but the display block that is supposed to be shown on the whatsapp is not displaying anythind to the user. Can you please review it as it is our last flow and our chatbot is almost done; just stuck at this phase?

@Rohit Joshi when can we expect a reply?

hello @sanskriti The issue is in your code execution node — {{last_received_message}} isn't a valid variable, so the order ID comes through empty and the API call never actually runs. Your Capture step already saves the order ID as FLOW.order_id, so just replace {{last_received_message}} with {{FLOW.order_id}} in your code and publish the flow. Let me know if you face any issue!

Hi @Rishabh we have made the changes considering your suggestions however the end result is still the same. Can you please check why this is happening as I have used the AI Copilot provided as well as the internal "generate code" feature in the code execution to fix it. However none of it worked.

Could you please share your project URL so I can take a closer look at the flow

Absolutely. https://chatbot.yourgpt.ai/dashboard/adb20105-08cb-40a9-93f3-66b378b9a32a/studio/flows/cf6c1813-d5fa-4e8c-a174-45b10cfcbc9f

We’ve made some changes to your flow and fixed the order lookup issue. Please publish the flow and test it once. Let us know if you face any further issues

@Rishabh I had saved and published the flow but the result while testing is still the same

The previous changes were not saved properly. I’ve now updated and published the flow with the fixes, including setting get_unconfirmed_orders: true in the order lookup. Could you please test it again from your end and let us know if the issue persists?

Yes, @Rishabh thankyou we have tested for various order ids and the flow is working perfectly now.