Roadmap
Changelog

Have something to say?

Tell us how we could make the product more useful to you. For Support reach out at hello@lamatic.ai.

Planned

Model Preference & Fallback

A dedicated UI to choose model preferences on project level. There will be different categories of models ( Tabs ) for Text | Embedding| Chat | Image | Audio | Transcript For Each category customer can create 5 Settings and reorder them. In each settings can choose 4 tabs ( Basic | Fallback | Best | A/B Test ) When using model selection in a workflow node, choose a preferred setting options which will populate the UI with credentials and model selection. ( By Default the first preference will be chosen or create a new preferences

Aman Sharma 10 months ago

1

💡 Feature Requests

In Progress

Test Case Expected Results

When creating Test Cases, capture expected results (in addition to capturing the name and test conditions as Lamatic does currently). Consider also, Using code checks and AI to find deviation and grade result quality. Use this quality score as an input for deciding whether to deploy an update. Assist in recommending the best option when A|B testing prompts, agents, workflows, models and other settings such as temperature. Using these results to create benchmarks. Measuring and alerting about “model drift” over time. Integrating “human-in-the-loop” strategies to expand Test Cases and quality checking. Added Later (based on feedback from another user): Make it easier to see the history of Test Case executions (without leaving Experiments). Marc Greenberg didn’t realize he could find the results in Logs, but also didn’t like having to dig through logs to find the execution details for a given test.

cwhiteman 10 months ago

1

💡 Feature Requests

Problem creating a new account + problem inviting member (with video)

Video 1: create a new account with a new email Entered email & pwd and clicked Sign Up. [0:32] Problem #1: Confirmation email not sent. After waiting 3 minutes, clicked “Resend confirmation email”. [3:00] Problem #2: Failed to Resend - captcha verification process failed All subsequent attempts to create an account with this email failed (see video). Video 2: invite Lamatic user to join a project Invited email to join a project. [0:00] After waiting for the invite email for 2 minutes, clicked “Resend invite”. Both invites then immediately showed up in my inbox. [2:00] Problem #3: original invite wasn’t sent until resend was clicked. Of course, I was both the sender & the recipient, so I knew to resend. Must be clear to recipient (after resend) what to do if they already have an account (see this ticket). If user figures out they have an account and try to reset password all sorts of errors ensued. I gave up trying to diagnose what’s going on, but here’s one of the PostHog recordings: https://us.posthog.com/project/74682/replay/0196deca-ac2f-73ff-be70-6e3df47821db. We really must QA all the ways to login since this is the first step in getting new customers (a broken or buggy experience kills our conversion).

cwhiteman 3 days ago

🐛 Report Bug

LLM Model Error Handling Improvement

Implement generalized error codes and smoother handling for model-related failures. This will help both users and platforms create more reliable alert systems and improve overall system Example for Open AI Code CodeOverview 401 - Invalid Authentication Cause: Invalid Authentication Solution: Ensure the correct API key and requesting organization are being used. 401 - Incorrect API key provided Cause: The requesting API key is not correct. Solution: Ensure the API key used is correct, clear your browser cache, or generate a new one. 401 - You must be a member of an organization to use the API Cause: Your account is not part of an organization. Solution: Contact us to get added to a new organization or ask your organization manager to invite you to an organization. 403 - Country, region, or territory not supported Cause: You are accessing the API from an unsupported country, region, or territory. Solution: Please see this page for more information. 429 - Rate limit reached for requests Cause: You are sending requests too quickly. Solution: Pace your requests. Read the Rate limit guide. 429 - You exceeded your current quota, please check your plan and billing details Cause: You have run out of credits or hit your maximum monthly spend. Solution: Buy more credits or learn how to increase your limits. 500 - The server had an error while processing your request Cause: Issue on our servers. Solution: Retry your request after a brief wait and contact us if the issue persists. Check the status page. 503 - The engine is currently overloaded, please try again later Cause: Our servers are experiencing high traffic. Solution: Please retry your requests after a brief wait. 503 - Slow Down Cause: A sudden increase in your request rate is impacting service reliability. Solution: Please reduce your request rate to its original level, maintain a consistent rate for at least 15 minutes, and then gradually increase it.

Vrijraj Singh 5 days ago

👏🏻 Feedback

Jobs Queue should provide more visibility

Users want to see how a job is progressing as well as the end result (the fact that the job completed successfully can mislead the user into thinking that there were no errors in the logs). A quick way to do this would be to add a button on the Jobs screen that links to the Logs screen (for that Job). This would’ve been helpful for my last 2 onboardings: Dor Bank & Sean Clarke. In Sean Clarke’s case, because he had set his flow up as Incremental, once he fixed the problem & redeployed, no records were inserted when he reran the vectorization flow (because the files themselves hadn’t been updated). This was confusing. LINK TO:

cwhiteman 10 days ago

💡 Feature Requests

Make deployment more intuitive and fun

Users are drawn to the Rocketship deploy button. They often click it and fail to deploy anything because they forget they must first activate their flow(s). Recommend modifying the current Deploy Project dialog box as follows: Remove Description (rarely does someone put anything useful here) Modify “Following changes will be deployed on edge”: Don’t include flows that were created and deleted (in other words, don’t show deleted workflows in the list as it’s confusing). Listed with most recently updated shown first. Provide a toggle to deactivate any flow in this list (so that it will be removed from the edge). Add “Following changes will not be deployed” List flows that have changes, but are not active. Listed with most recently updated shown first. Provide a toggle to activate any flow in this list (so that it can be deployed).

cwhiteman About 1 month ago

👏🏻 Feedback