how to use datasize and timeout is not the most intuitive
I have a larger datasize and a huge timeout. I think the assumption was that if we get a bigger chunk of data, as long as we give ourselves a ton of time to get it, it'd be fine. but in practice, a similar ratio of smaller chunk to smaller time is what succeeded.
when it did fail, it took the full timeout, then returned the error.
We fixed it for the one batch job, but then forgot another to set it for.
Is it possible to make it a global setting?
Or can someone explain why it would need to be different for different batch jobs?
ECC batch jobs datasize/timeout
-
- Posts: 472
- Joined: November 16th, 2021, 11:15 am
- Contact:
-
- Posts: 329
- Joined: August 26th, 2021, 9:18 am
- Contact:
Re: ECC batch jobs datasize/timeout
There is task #10952 to address the data size confusion.
word count: 10
-
- Posts: 572
- Joined: August 26th, 2021, 9:56 am
- Contact:
Re: ECC batch jobs datasize/timeout
This change has been implemented as of DesignTime Revision 2463 and RunTime Revision 1125 and ECC Revision 127.
word count: 18