Scheduled Tasks not running any tests

Get Support
1

The schedule tasks has worked for me in the past, but now its not finding any of the tests in the Execution time comes back with a offset of epoch 0. If i run the same test locally it works well. This used to work just fine but has stopped functioning. I have rebuild the test runner and still seeing the same issues.

Execution Time
1969-12-31 16:00:00
Execution Tool
Runner v0.0.1
image.png

2

The notification is sent as it completed, but it doesn’t find any tests and has a impossibly long run time shown.

3

Thank you for your feedback. The newly launched runner on my end is working normally with both manual and scheduled runs. Could you please provide more details:

  1. Current runner version
  2. Current app version
  3. Current running behavior
  4. Is it consistently showing as online?
  5. Has the runner’s network environment changed?
    5dc59f77-01f1-41ac-96be-fa85401f2034.jpeg
    5dc59f77-01f1-41ac-96be-fa85401f2034.jpeg812×382 62.1 KB

    53fc1a61-d2dc-4e4b-ad47-02a811bcfd31.jpeg
    53fc1a61-d2dc-4e4b-ad47-02a811bcfd31.jpeg1494×500 136 KB

    e47073ba-8898-49d2-ba84-f061244ba7af.jpeg
    e47073ba-8898-49d2-ba84-f061244ba7af.jpeg1021×950 69.4 KB
4

Same version as you of the runner. 1.8.1. Always shows running.

image.png
image.png1219×225 29.1 KB

5

I just get no tests. No Errors or any logs i can see anywhere.

image.png
image.png1269×450 99.5 KB

6

Thank you for the details. I couldn’t reproduce the issue locally. To help troubleshoot:

  1. Create a new scheduled task to run the same scenario.
  2. Create another scheduled task to run a different scenario (e.g., use the sample project in your team).
  3. Check the runner logs (refer to our help docs for guidance).

Let me know the results.

56f3c534-8ecf-4854-a69f-fe25526be038.jpeg
56f3c534-8ecf-4854-a69f-fe25526be038.jpeg1610×960 73.3 KB

7

the docker logs are showing “invalid environment id”, it is able to see the test group though becuase in this case it is able to start it and see the test name is “Authentication” but then gets a 403.

image.jpg
image.jpg1488×1030 192 KB

8

Based on the issue described, please check:

  1. Whether the environment being used is private
  2. If the referenced environment has been deleted
  3. When modifying other environments, check if step execution is displayed properly
    0f641ae7-5076-4685-b2db-0a9e81a2eca5.jpeg
    0f641ae7-5076-4685-b2db-0a9e81a2eca5.jpeg1766×564 105 KB
9

it was private and changing that helped. Can it not be private for it to work on the runner?

10

Yes, private environments are not supported.