My daily counter did not run today

Server Code
1

I have a daily counter running, but today it did not run as expected. Could you please have a look.
Thanks.

2

Hi @Jorg_Beyer

I would love to, could you please provide your appId and how/where I can find the counter

Regards,
Vlad

3

AppId 476E605C-5D5F-5F4E-FF3B-264AC1B25F00

4

I can see your timer was invoked today

2023-02-17 15:31:07,590 | SERVER_CODE |  INFO | [1389540] [B488614A-04CB-48AB-85F8-F2B25620B885] [INVOKE TIMER]
5

I did start it manually to see whether there are obvious errors. That was at that time. Usually the timer start at 13:00 UTC

6 
2023-02-17 13:00:00,314 | SERVER_CODE |  INFO | [1197026] [9CAAE2C9-5372-43DA-A15D-1DFBB5B30256] [INVOKE TIMER]
2023-02-17 13:00:10,314 | SERVER_CODE | ERROR | [1197026] Task execution is aborted due to timeout
7

Ok, any idea why a timeout can happen? It is not a data intensive task. And, where can I find the above listed log lines?

8

I can see you update date in a data table in a loop, it could be the reason

Codeless - BL - Backendless 2023-02-17 18-22-21
Codeless - BL - Backendless 2023-02-17 18-22-211254×936 72.6 KB

1 Like
9

try to add more logs to see where it gets stuck

1 Like
10

It always gets a timeout at the Upsert. I have an API request that takes approx 5 sec for getting the data from an external data provider. After that, I want to make 16 upserts into a small table (see pic).

image
image1864×84 11.2 KB

An upsert can take up to 1 sec, multiplied by 16 upserts the script runs into the timeout.

Any idea what to optimize?

11

Would Bulk Upsert be applicable here?

1 Like
12

Very good idea, never thought about it. I give it a try.

13

Test run of Timer showed significant improvement. I am looking forward to the next scheduled run. Thanks for the quick help.