Not getting a new test run id

Making Speckle Insiders - Automate
1

i create a new test automation, which generates an id

Reporting run status with content: {'projectId': '0f41ce0842', 'functionRunId': 'aa2145a7ab88511', 'status': 'SUCCEEDED', 'statusMessage': 'WARNING: Automate assumed a success status, but it was not marked as so by the function.', 'results': {'version': 1, 'values': {'objectResults': [], 'blobIds': []}}, 'contextView': '/projects/0f41ce0842/models/19e33ca492@b179a7092e'}

but if i run it again, the log doesn’t show a new id

❯ python test.py
Reporting run status with content: {'projectId': '0f41ce0842', 'functionRunId': 'aa2145a7ab88511', 'status': 'RUNNING', 'statusMessage': None, 'results': None, 'contextView': None}
Traceback (most recent call last):
...
packages\gql\client.py", line 248, in execute_sync
    return session.execute(
           ^^^^^^^^^^^^^^^^
.venv\Lib\site-packages\gql\client.py", line 1028, in execute
    raise TransportQueryError(
gql.transport.exceptions.TransportQueryError: {'message': "Invalid status change. Attempting to move from 'succeeded' to 'running'.", 'locations': [{'line': 2, 'column': 3}], 'path': ['automateFunctionRunStatusReport'], 'extensions': {'code': 'FUNCTION_RUN_REPORT_STATUSES_ERROR', 'statusCode': 400}}

…which creates an error. i want to say that a couple of months ago, i did not get this.

2

Thanks for reporting this @majidaldo this is a known issue and I agree it is extremely frustrating. Nothing you’ve done wrong this is entirely an execution race condition so far as I understand it. The automate backend team are aware and apologies if it causes issues for you usually you just run it again and it doesn’t happen. It is why we separated the reported error state to show exception as distinct from other fail types. exception is always infrastructural.

Try a second run.

3

unfortunately, the problem persists.