In the backend - trying to understand why my action to look up details of an upcoming fixture is no longer working having worked perfectly for more than a month, I click the magnifying glass to see what knowledge and what actions where used and get this:
We’ve recently updated our submission system to use a single stream, similar to how other LLM providers handle submissions. It was a major update, but ultimately for the better. We’re aiming to support MCP soon, and this brings us one step closer.
Please include the Pickaxe, the prompt used, and any other relevant details that can help us debug further.
I get the need for change for a better product but surely all this should be done on a development version or a staging site that we can text fully. My site has been broken all day and I’m in the middle of due diligence from an investor and a sports governing body about using my PA across the whole sport!
This was so problematic - I had to write code to keep users out today with a maintenance screen!
query was ‘LA Galaxy’ - it then uses an action to fetch the current time then uses a perplexity action to look up fixtures… not working at the moment and when I click on the magnifying glass I get the error above.
Until today, this would work perfectly. Today it doesn’t work and right now… if I enter it, it asks for further clarification and doesn’t even attempt to run the actions.
@stephenasuncion I’ve always used open ai 4.1 mini for this as it performed better when i set it up originally a month ago. I’ve just tried it in o3-mini and it works with both actions fired in sequence BUT, the context returned isn’t as strong as 4.1 mini previously so I don’t really want to leave it on o3-mini as it has been working fine in 4.1 mini.
@stephenasuncion Its just past 01:00 Sunday here and I need to call it a day as I have been trying to sort this mess out since early Saturday morning. The PA does not work on o3-mini so I need to run it the way i did previously via 4.1-mini. I need to be able to run two actions in series… date first, fixture details next as this is the only way it works at the moment without hallucinating an answer. Can you let me know when actions are likely to be back to how the were on Friday and working with 4.1-mini please?
I made some changes, I believe its better now, just tried with my own Pickaxe.
What you got when you tried it @stephenasuncion was worlds apart form what users where getting last week. I have now fully rewritten the prompt to work. BUT its not ideal that every time PA changes something foundational, a complete rewrite of the prompt is required to get it to work again - and this is after you have fixed issues such as actions not firing. I appreciate the help but I lost a day trying to sort this after a system change I had no notice of, or control over!
@ihmunro I’ve frequently posted about how I have used script to add in whatever I want. You just need to keep in mind that PA may change the use of various Tailwind classes and that may temporairly break some of the styling or additional button use.
At present, I have the capability to:
- temporarily replace my studio with a complete maintenance page whilst changes are made
- add in action buttons after a chat repsonse, add in PA level FAQ and Support Buttons.
- add in chat deletion buttons on chat history
- add in voice/dictation capability
- restyle the front end
- customise the studio butotns on the home page and add in my own
- add in google tracking and SEO at PA level
- completely restyle the PA chat flow with html, css and smart tables dynamically.
- produce condensed 3 minute minicasts that are audio of why the output from my PA makes sense.
My suggestion, since the code blocks are large, you take a look at one of my studios and view source as the code is all there and you can copy paste it.