19
permissions:
20
contents: write
21
pull-requests: write
22
+ issues: write
23
env:
24
COMPOSIO_API_KEY: ${{ secrets.COMPOSIO_API_KEY }}
25
132
run: |
133
gh pr edit "$PR_NUMBER" --add-reviewer "$AUTHOR" || \
134
gh pr edit "$PR_NUMBER" --add-reviewer "Sushmithamallesh"
135
+
136
+ # A silent failure here is invisible: the workflow stops refreshing
137
+ # public/data/toolkits.json, the docs site keeps building from the last
138
+ # good commit, and nothing 500s — new toolkits simply 404. That is how a
139
+ # credential failure went unnoticed for 60 consecutive runs. File one
140
+ # tracking issue and leave it open until someone fixes the cause.
141
+ - name: Open tracking issue on failure
142
+ if: failure()
143
+ continue-on-error: true
144
+ env:
145
+ GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
146
+ GH_REPO: ${{ github.repository }}
147
+ LABEL: docs-data-sync-failure
148
+ RUN_URL: ${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}
149
+ EVENT_NAME: ${{ github.event_name }}
150
+ run: |
151
+ gh label create "$LABEL" \
152
+ --color B60205 \
153
+ --description "Scheduled docs data sync is failing" 2>/dev/null || true
154
+
155
+ existing=$(gh issue list --label "$LABEL" --state open --limit 1 --json number --jq '.[0].number // empty')
156
+ if [ -n "$existing" ]; then
157
+ echo "Issue #$existing is already open for this failure; not filing a duplicate."
158
+ exit 0
159
+ fi
160
+
161
+ gh issue create \
162
+ --title "Docs data sync is failing" \
163
+ --label "$LABEL" \
164
+ --body "The scheduled \`Docs - Update Data\` workflow failed.
165
+
166
+ - Run: $RUN_URL
167
+ - Trigger: \`$EVENT_NAME\`
168
+
169
+ **Impact:** while this is red, \`docs/public/data/toolkits.json\` stops being
170
+ refreshed. docs.composio.dev/toolkits is statically generated from that file, so
171
+ toolkits added to production after the last successful run have no page and
172
+ return 404. The site stays up, which is why this fails silently.
173
+
174
+ **First thing to check:** the \`COMPOSIO_API_KEY\` secret must have **production**
175
+ read access against \`backend.composio.dev\`. A staging-only key returns 401 here.
176
+
177
+ This issue is filed once and left open until the cause is fixed; it will not be
178
+ re-filed on every run."