Troubleshooting guides by topic
Automation
Scheduled jobs, integrations, CI/CD workflows and alerts.
24 English guides in this category
Business process automation: what should you automate first?
Identify repetitive tasks, calculate potential savings and start with forms, CRM integrations and reminders instead of overcomplicating AI.
Read the solutionGitHub Actions: artifact expired before downloading
When trying to play the old build download-artifact does not find a file.
Read the solutionGitHub Actions: artifact not found in another job
Build saves the file, but the next job cannot download it or fetch an outdated artifact.
Read the solutionGitHub Actions: Automated Commit Conflicts with Changes to Main
The machine created a commit on the old repository state and git push reports non-fast-forward.
Read the solutionGitHub Actions: Concurrency Settings Cancel the Wrong Build
After the push series one launch is canned and there is no publication.
Read the solutionGitHub Actions: environment secret empty despite the correct name
The secret is found in the production environment, but the job is not given its value.
Read the solutionGitHub Actions: git merge-base Fails with a Shallow Clone
The change analysis script cannot determine a common branch ancestor, even though repo works locally.
Read the solutionGitHub Actions: git push ends with 403 Resource not accepted error
Job passes tests, but cannot save the commit to the repository.
Read the solutionGitHub Actions: Invalid format when writing GITHUB OUTPUT
Job ceases to work after writing a multi-line value to the output file.
Read the solutionGitHub Actions: Job Stuck in Queued State
In the Actions job panel, it has a state ofqueued much longer than normal run.
Read the solutionGitHub Actions: Matrix Fail-Fast Cancels Remaining Tests
One combination of Node and the operating system fails and the other tests do not finish.
Read the solutionGitHub Actions: npm cache does not fix an error after changing lockfile
After changing package-lock.json CI continues to report dependency errors, and diagnostics focus on cache.
Read the solutionGitHub Actions: npm Cache Misses on Every Run
Another run re-downloads all dependencies despite the configured cache.
Read the solutionGitHub Actions: one push runs workflow twice
After one merge two almost identical runs appear and can publish the same file.
Read the solutionGitHub Actions: push does not run CI through paths
The change in the code file does not trigger the expected workflow.
Read the solutionGitHub Actions: push to GHCR returns denied 403
Workflow builds an image of Docker, but publication to ghcr.io does not have permission.
Read the solutionGitHub Actions: reusable workflow does not receive the secret provided
The called workflow works, but the token used by his job is empty.
Read the solutionGitHub Actions: Run workflow button is not visible
Workflow exists in the working branch, but there is no manual launch option.
Read the solutionGitHub Actions: Scheduled Workflow Is Not Running
Workflow with cron runs through Run workflow, but does not appear running at scheduled time.
Read the solutionGitHub Actions: Secret Environment Variable Is Empty
Workflow shows an empty environment variable and the code reports no API key.
Read the solutionGitHub Actions: Secrets Unavailable in Forked Pull Requests
The PR test from the outside fork does not see the secret, although the workflow main works properly.
Read the solutionGitHub OIDC: token is correct, but audience mismatch
Calling the service after receiving the OIDC token ends with 401 with an Audience or Issuer error.
Read the solutionGitHub: Required status check remains Pending despite the green CI
PR has correct tests, but the branch rule waits for nonexistent status.
Read the solutionHow much does customer-service automation cost?
Prices for form processing, CRM handovers, notifications and chatbots, including the factors that affect implementation.
Read the solution