You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After an error in the workflow definition, the workflow pod constantly logs the error Workflow is not ready yet. - and the actual error gets burried somewhere. This is just from user experience point of view - but something that can be improved on. At the very least - the frequency of logging same error should be reduced in a retry/backoff kind of mechanism.
workflow time="2018-08-20T11:44:15Z" level=info msg="Resolving function: http" component=fnenv.fission
workflow time="2018-08-20T11:44:15Z" level=info msg="Resolving function: whalesay" component=fnenv.fission
workflow time="2018-08-20T11:44:15Z" level=info msg="Event added: INVOCATION_CREATED" aggregate=invocation/wi-feef01bd-8d75-4472-9819-0d7b562c5fcf nats.subject=invocation.wi-feef01bd-8d75-4472-9819-0d7b562c5fcf parent=/
workflow time="2018-08-20T11:44:15Z" level=error msg="Workflow is not ready yet." wf.status=PENDING
workflow time="2018-08-20T11:44:15Z" level=error msg="Action '*workflow.ActionParseWorkflow' failed: failed to resolve tasks in workflow: failed to resolve function 'whalesay' using clients 'map[internal:0xc42000c610 fission:0xc42000c628]': Resource not found - NotFound" component=controller.workflow
workflow time="2018-08-20T11:44:15Z" level=error msg="Workflow is not ready yet." wf.status=PENDING
workflow time="2018-08-20T11:44:15Z" level=error msg="Workflow is not ready yet." wf.status=PENDING
workflow time="2018-08-20T11:44:16Z" level=error msg="Workflow is not ready yet." wf.status=PENDING
workflow time="2018-08-20T11:44:16Z" level=error msg="Workflow is not ready yet." wf.status=PENDING
workflow time="2018-08-20T11:44:16Z" level=error msg="Workflow is not ready yet." wf.status=PENDING
workflow time="2018-08-20T11:44:16Z" level=error msg="Workflow is not ready yet." wf.status=PENDING
workflow time="2018-08-20T11:44:16Z" level=error msg="Workflow is not ready yet." wf.status=PENDING
The text was updated successfully, but these errors were encountered:
After an error in the workflow definition, the workflow pod constantly logs the error
Workflow is not ready yet.
- and the actual error gets burried somewhere. This is just from user experience point of view - but something that can be improved on. At the very least - the frequency of logging same error should be reduced in a retry/backoff kind of mechanism.The text was updated successfully, but these errors were encountered: