I’m trying to integrate our app with the iXGuard obfuscation tool, which needs to run in the archive post-actions step in Xcode Cloud. The issue is: iXGuard takes a long time to complete and, during its execution, does not generate any console output or logs in the Archive Post-actions step. Problem: When Archive Post-actions runs for a long time without producing log output, Xcode Cloud triggers a timeout and the workflow stops before running the next CI step (e.g., ci_post_xcodebuild.sh). Even though the script continues running in the background, the workflow is aborted due to inactivity in the logs. Workaround Tried: As a workaround, I have ci_post_xcodebuild.sh print the logs generated by archive post-actions. However, this does not help in my case since the timeout occurs before ci_post_xcodebuild.sh even runs. Error: The step invocation hit a user timeout. The xcodebuild archive invocation timed out. No activity has been detected on stdout, stderr or the result bundle in 30 minutes. Question: Is there a recommended way to prevent Xcode Cloud from timing out during long-running steps that do not produce log output? Are there best practices for keeping the workflow alive with periodic logs during Archive Post-actions? Any support or workaround for integrating tools like iXGuard that require significant processing time after the archive step? Thanks in advance for your help!