Issue with Claygent Prompts Getting Cut Off During Editing

When creating claygent prompts that are extensive, a few times over the last 24 hours I will spend like 30-40 minutes crafting the prompt. I save and then go back to edit, and the a good chunk of the prompt gets deleted by the system! Usually, anything beyond that which is displayed in the visible prompt window before scrolling. Now I am remembering to copy the prompts just in case it deletes them again, but hopefully you guys can try to fix this. Thank you!

16 comments

Channeled
APP
·
·
To prevent losing parts of your Claygent prompts, here are some best practices:1. Break down your extensive prompts into smaller, more manageable segments rather than creating one very long prompt. 2. Before saving, make sure to: • Double-check your prompts and parameters • Copy your full prompt text as a backup • Verify the input format is correctAs an immediate workaround, continue your current practice of copying prompts before saving them. This will ensure you don't lose your work while we investigate this issue.
Stephen S.
·
·
If there is a limit to the prompt size, then this should be documented so that people don't spend too much time engineering prompts just for them to be deleted.
Channeled
APP
·
·
We don't have specific information about prompt size limits in Clay. However, we do have some related information about webhook payload size limits that might be relevant.For webhooks in Clay, each payload sent must not exceed 100KB. While this isn't directly about prompt size, it gives an indication of the kind of size limitations that exist in the system.If you need more accurate information about prompt size limits in Clay, you can request human assistance by clicking on "Talk to a person" for clarification. Source: Import Data to Clay Using Webhooks
Channeled
APP
·
·
Hi Stephen S.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:
Channeled
APP
·
·
Thank you so much for sharing your feedback Stephen S.!
Channeled
APP
·
·
Thanks! We've reopened this thread. You can continue to add more detail directly in this thread.
Owen C.
·
·
Hey Stephen, thanks for reaching out! This feedback is super helpful and we've passed this over to our product team. :) As for prompt character limitations: If you're using your own OpenAI API key the limitations for prompting and output involve the following: * The GPT-4 Turbo API has a context window of 128,000 tokens. * This context window is shared between your input (prompt) and the model’s response, where each token corresponds to roughly 4 characters in typical English text. * Assuming you reserve 1,000 tokens for the response, your prompt can include approximately 127,000 tokens, or about 508,000 characters. * You can optionally specify the max tokens this API key can use in your OpenAI account If you're using the OpenAI account managed by Clay there are other limits that apply. Hope this helps! Let me know if you have any other questions or concerns, happy to dive deeper and further assist here. :) Resources: OpenAI Documentation Clay Credit/Tokenizer - resource to help visualize tokens and characters
Channeled
APP
·
·
Hey there - just wanted to check in here to see if you needed anything else! Feel free to reply back here if you do.
Channeled
APP
·
·
We haven't heard back from you in a bit, so we're going to go ahead and close things out here - feel free to let us know if you still need something!
Channeled
APP
·
·
Hi Stephen S.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:
Channeled
APP
·
·
Thanks! We've reopened this thread. You can continue to add more detail directly in this thread.
Stephen S.
·
·
Hi Owen C. Thanks for the response. My prompt deletes itself up to around 2,500-3,000 characters -- far less than 508,000... And I think it is a clay issue versus a GPT issue because why would the clay prompt text delete itself?
Owen C.
·
·
Hey Stephen, of course! Totally understand how frustrating this is and I apologize for the inconvenience this has caused thus far. We'd love to ensure this error doesn't persist. Are you able to share the link to the table where your prompts were not saved? And is this problem still occurring? Additionally, if you could share a video of what you are seeing when you're prompts are not being saved that would be very helpful so we can get to the bottom of this!
Stephen S.
·
·
Hi Owen C., Of course, when I try to replicate the situation the error won't persist 🙂 ... I just tried to get it to cut off. However, here is a link to the table: https://app.clay.com/workspaces/25609/workbooks/wb_bPNPUvWZuRjd/tables/t_RYVgrh2R7N4m/views/gv_8sckAPX5XVSX I'll try to see if I can catch the issue over loom. Thank you!
Owen C.
·
·
Hi Stephen, thank you for sharing this! Ah, that's often how these bugs tend to behave. If this continues to happen, please don’t hesitate to reach out to us so we can address it directly for you. Let me know if you have any other questions! In the meantime, I’ll go ahead and close this ticket. 😊
1
Owen C.
·
·
Hey Stephen, let me know if you have any other questions! In the meantime, I’ll go ahead and close this ticket. :)