1 Answer
- Newest
- Most votes
- Most comments
0
Update: changing the base capacity led to being able to run queries longer than 600s.
So, most likely the max_query_execution_time
rule redeployed with it.
Is this the expected behavior? Otherwise, it I would classify this as a bug in a basic functionality.
answered 2 years ago
Relevant content
- asked 2 years ago
- Accepted Answerasked 2 years ago
- asked 2 years ago
- Accepted Answerasked 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 4 months ago