Open
Description
A seeing the following behaviour on lilypad deployed for waterlily
- job is found in the contract
- bacalhau job is submitted
- can see job in "running" state from log output
- job completes
- we then get
job not found
errors - this causes an error state and a re-try of the whole job
- a new bacalhau job is submitted and the above steps repeat
The bacalhau cluster we are using has a single requester node ai-art-requester.cluster.world
I was also seeing the same loop happen with estimate gas
errors rather than job not found
errors