Where: web portal, creating a job from Katapult. Needs: the Org Admin role, for the fix.
When you finish: your organization has a working Katapult key stored and the job creates.
What you see
On the Select Katapult jobs step, the list shows "Katapult jobs couldn't be loaded." with a Try again button. Try again can help if Katapult was briefly unreachable. If you get the same message again, the key is the problem.
On an older job page, the same problem reads "Error loading jobs" with Retry. The cause and the fix are the same.
Short answer: a Katapult key is saved, but Katapult did not accept it. The key may be wrong, revoked or expired, or the Katapult user it belongs to may not have API access. If no key were saved at all, Cloneable would ask you to enter one instead of showing this message.
Fix it
Open Settings, then Secrets vault.
On the Platform secrets tab, look for a credential named KATAPULT_API_KEY.
If it is missing: Create secrets, Add platform secrets, pick Katapult, paste the key, Save all secrets. Full detail in Store the credentials your integrations need.
If it is there, it has probably stopped working. Katapult keys rotate, get revoked or expire. Generate a fresh one in Katapult, then choose the pencil Edit button on the key, paste the new value and choose Save. Do not add a second key; Cloneable refuses it without showing an error.
If a fresh key fails too, ask your Katapult admin to turn on API access for the Katapult user the key belongs to.
Try creating the job again.
This surfaces at the worst moment, usually when someone is trying to get a crew out. Checking that your Katapult jobs load right after you store the key catches it early.
Related