Troubleshooting
Common curator issues and how to resolve them.
Login issues
Problem: I can’t log in to the admin console.
- Ensure you are using the correct URL (production URL from the platform team; local:
https://localhost/admin/login). - Use the exact email address your account was created with.
- If you have forgotten your password, contact the platform admin to reset it.
Problem: My login redirects me back to the login page with no error.
This sometimes happens if your browser is blocking the session cookie. Try:
- Clearing cookies for the admin domain
- Using a private / incognito window
- Checking if your browser blocks cookies from localhost
Ingestion issues
Problem: No new items are appearing in the Ingested Items queue.
- Check Ingestion Sources → confirm the source is active (
is_active = true). - Open the source record and check Last Scraped and Last Error.
- If the source uses n8n, open n8n Executions from the source record to inspect recent workflow runs.
- Check that the n8n workflow for this source is enabled in n8n (
http://localhost:25678in local dev). - If token or injected-variable drift is suspected, use Update n8n Workflow on the source record to refresh the current token and source URL.
Problem: I promoted an item but it did not appear on the platform.
Promotion creates or updates the canonical record but does not control platform visibility directly. Check:
- Events: Is the event in
publishedstatus? Is the event date in the future? - Places: Is the place active?
- Stories: Is the story topic active and accessible in the mobile app’s Explorer section?
Problem: A promoted event has the wrong venue or coordinates.
- Edit the canonical Event record and re-link it to the correct Place.
- If the Place record itself has wrong coordinates, edit the Place directly.
Queue and background job issues
Problem: Ingestion jobs are queued but not processing.
- Check that the Horizon queue worker is running:bash
php artisan horizon:status - If Horizon is paused, resume it:bash
php artisan horizon:continue - In the Docker stack, Horizon runs as a separate container. Confirm it is healthy:bash
docker compose -f compose.production.yaml -f compose.local.yaml ps
Getting more help
If these steps do not resolve the issue, contact the Kubuli platform team with:
- The source name and URL (for ingestion issues)
- The item ID or error message from the source record or
n8n Executionsview - A screenshot of the error if available