Add Error Handle Logic - Failed Create Export Artifact

[marc-denman]

Thanks in advance for this nice action. Helps with compliance no doubt. I attempted to execute this against an enterprise cloud account with multiple organizations. It appears one of the Orgs does not contain and repositories to report against. As a result, it seems the action stops at that point and does not continue so that it can finish and generate the csv artifact. @SvanBoxel Here is the error message:

Start collecting for organization
⏸ No data found for , probably you don't have the right permission
Cannot read property 'samlIdentityProvider' of null
⚛ Normalizing result.
Uploading chunk of size 4194304 bytes at offset 0 with content range: bytes 0-4194303/5702770
Uploading chunk of size 2595943 bytes at offset 0 with content range: bytes 0-2595942/2595943
(node:1899) UnhandledPromiseRejectionWarning: Error: read ECONNRESET
at TLSWrap.onStreamRead (internal/stream_base_commons.js:201:27)
(node:1899) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:1899) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

[marc-denman]

Hello again @SvanBoxel - Hoping you will be able to find some time to review the issue I opened previously. Not much of a developer myself so hoping you or another team member can review and help resolve. This report would be very helpful but due to error I noted, seems like something does not complete and a CSV artifact is never produced.

Thanks again for consideration.