Error 99: Connected to... about powerplatform-actions HOT 3 CLOSED

@19JoaoPereira97 The way we debug tooling issues in our own workflows is using the pac CLI's trace logs, by adding an upload-artifact action unconditionally at the end of the workflow, see e.g.

the logs are placed in this folder on the runner:
./dist/pac*/tools/logs/pac-log.txt

My suspicion is, this is an error returned from the Dataverse/CDS side, but clearly, the pac CLI &export-solution action is not surfacing that error properly (which is a bug on our side, sri)

from powerplatform-actions.

I was getting the exact same error message and was able to solve the problem by adding the parameter run-asynchronously: true to the export-solution action. So I guess it was a timeout issue, at least in my case. The error message wasn't very helpful in figuring this out, unfortunately.

@davidjenni I tried your suggestion but the resulting log file was empty. This is what I added to the action file:

- name: upload pac CLI logs
      if: always()
      uses: actions/upload-artifact@v2
      with:
        name: pac-cli-log
        path: ./logs/pac-log.txt

The artifact was created but the file was empty. Did I miss anything?

from powerplatform-actions.

@nkirstein assuming that any of the powerplatform-actions have run, that log file is NOT expected to be empty, see e.g. this workflow from this repo:
https://github.com/microsoft/powerplatform-actions/actions/runs/1147496290#artifacts

from powerplatform-actions.