Hi everyone,
I have a process that runs daily and queries the Adobe Query Service using a non-expiring credential. Recently, this query has been hitting the 600-second timeout limit and failing.
Interestingly, when I run the exact same query using an expiring credential, it works without any issues. Unfortunately, using expiring credentials is not an option for me because this is an automated process that relies on the non-expiring credential.
Does anyone know why this behavior might be happening? Are there any solutions or workarounds to ensure the query completes successfully with the non-expiring credential?
Any insights would be greatly appreciated. Thank you!
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
If you're attempting to use a CTAS statement and automate the process it is best to schedule the query.
You can limit the results by placing a limit.= N on the initial sql statement. Once this is completed you can schedule the query for lights out execution.
You can check this guide for the timeout.
I've already gone through the documentation, and unfortunately, my query is quite simple and cannot be optimized further.
What I'm trying at the moment is to use CTAS (Create Table As Select) so that the query runs entirely within the platform, and I send only the information I need to a smaller dataset. Additionally, I plan to set up a scheduled query to automate this process and ensure the data is consistently updated for faster querying outside of AEP.
Views
Replies
Total Likes
If you're attempting to use a CTAS statement and automate the process it is best to schedule the query.
You can limit the results by placing a limit.= N on the initial sql statement. Once this is completed you can schedule the query for lights out execution.