Workflow Automation: Errors and Troubleshooting Tips
When your flows aren’t working as expected, the best first step is to check the Flow Logs.
Most errors will appear in the Errors Only view. For more complex issues or to trace the sequence of actions, review the Actions Only or Everything views for detailed insights.
To stop a flow from running, simply deactivate it.
Tip:
The Developer Page for the Podio app is useful not only for troubleshooting hook events but also for diagnosing field-specific errors by referencing the Field ID.
Below you will find multiple Error messages along with their Symptoms, Causes and solutions.
ERROR
| Symptom |
Cause |
Solution |
| Could not authenticate to Podio with sharing user |
Sharing action uses a member who is not an Admin of the workspace |
Adjust the “Shared By” user to an Admin |
FatalPHPError
| Symptom |
Cause |
Solution |
| Memory Exhausted! |
Collecting too many items overwhelms memory |
Reduce the number of items being collected. Check here for more PHP errors |
PHPError
| Symptom |
Cause |
Solution |
| PHP Error in eval: “”==”” (calculation invalid) |
Calculation error in a Flow action |
Use Simulate Vars on a Podio item to check calculations |
PodioBadRequestError
| Symptom |
Cause |
Solution |
| Missing mandatory field name |
Required field token is blank or missing data |
Check data in field tokens; if a field is required, ensure it has a value before triggering the flow |
| The referenced item is not valid |
Referenced item is deleted or invalid |
Remove the referenced item and replace with a valid item |
| Multiple is not allowed for field ‘##’ |
Attempting to set multiple values on a field that doesn’t allow multiple selections |
In the destination Podio app, allow multiple choice for Category/Relationship/Contact fields or correct the field id via the app developer page |
| Invalid value ‘##’ (string): must be integer or object |
Contact field token returns a string where an integer/object is required |
Wrap the token in intval() to force an integer |
| A value is required for either ‘start’, ‘start_date’, or ‘start_utc’ |
Action updates End Date only (missing Start Date) |
Add a step to update the date field using the item’s current value (start date) |
| Invalid value ‘31 Mar 2017’ (string): Must be date in YYYY-MM-DD |
Date token is not in Podio’s required format |
Create a custom variable to format the date as YYYY-MM-DD |
| field.app.deleted |
Field was deleted or changed in Podio |
Refresh from Podio in Workflow Automation to update app data |
| Last view can only be used by users |
Get View action cannot collect the specified view |
Refresh from Podio and confirm the action collects the correct view; resave the flow |
PodioForbiddenError
| Symptom |
Cause |
Solution |
| Must be at least light on user to perfom this operation |
Contact in the specified field is not (or no longer) a workspace member |
Remove the contact member before triggering the flow |
| The app with id ## does not have the right view on profile with id ## |
Contact reference is not a valid member in the destination workspace |
Add the user in the contact field to the destination workspace, or remove from the item |
| The app with id ## does not have the right comment on item with id ## |
App settings do not allow comments |
Update app settings; refresh from Podio in Workflow Automation |
| The app with id ## does not have the right update on item with id ## |
App does not permit edits by users |
Enable edits in app settings or change Action Authentication to an Admin member |
| The app with id ## does not have the right add_file on item with id ## |
App does not allow files to be added to items |
Enable files in app settings (Modify Template > wrench) |
| The user with id ## does not have the right view on widget with id ## |
Main account user is not an Admin of the workspace (insufficient widget privileges) |
Promote main account user to Admin in the app/workspace |
| The user with id ## does not have the right grant_view on item with id ## |
Sharing user is on a Basic/Free plan |
Upgrade to Podio Plus or Premium |
PodioGoneError
| Symptom |
Cause |
Solution |
| Gone |
App changes not synchronized into Workflow Automation |
Refresh from Podio to update workspaces |
| Item has been deleted |
Flow triggered on an item that was deleted (often on date-trigger midnight runs) |
Resave date-triggered flows and/or add a Wait/Delay before any delete step |
| File has been deleted |
Workflow Automation tried to download/access a file or image that no longer exists |
Ensure the image/file is from a public source and avoid race conditions (other flows deleting the image) |
PodioInvalidGrantError
| Symptom |
Cause |
Solution |
| Sorry, your OAuth grant has expired |
Podio auth token is invalid (API key revoked, password changed, long inactivity) |
Main account/sharing user must sign in to Workflow Automation to re-authorize |
PodioNotFoundError
| Symptom |
Cause |
Solution |
| No matching operation could be found. Missing parameters:source |
Attempt to attach a file to Podio but the file is missing |
Ensure the file exists before attach; commonly occurs with images |
PodioUnavailableError
| Symptom |
Cause |
Solution |
| Single API call generated a 504 |
API call temporarily unavailable; flow continues but results may be unpredictable |
Check all involved items for consistent data; use log to get relevant item IDs |
RightSignatureError
| Symptom |
Cause |
Solution |
| Number of names does not match number of email addresses (omitting names) |
Email/name counts do not match RightSignature template roles |
Ensure number of emails equals number of names and matches roles in the RS template |
| There was an error with your RightSignature integration. Please reconnect |
One of more fields in the RS action block are empty/invalid |
Fill all fields in the RightSignature Template Action; reconnect RS account if needed |
| Exit with code 1 due to network error: ProtocolUnknownError |
Workflow Automation cannot access/read a resource used by the PDF (script/style unavailable) |
Ensure all PDF resources are hosted and accessible |
SMSError
| Symptom |
Cause |
Solution |
| Failed sending SMS to +119999999999 - Invalid recipient |
Phone number format invalid |
Adjust phone number to correct format |
| Failed sending SMS to +119999999999 - Throttled |
Service blocks multiple messages to the same number within short interval |
Wait at least 60 seconds between SMS messages |
SMTPError
| Symptom |
Cause |
Solution |
| Failed sending email: “SMTP Error: Data not accepted” (PHPMailer) |
Microsoft Office requires email to be sent by the authenticated user; From address mismatch |
Update the From Address to match SMTP login credentials |
| Failed sending through smpt.gmail.com: “SMTP Connect() failed” (PHPMailer) |
Assigned SMTP server failed to connect/credentials incorrect |
Disconnect SMTP, re-enter credentials, send a test message |
Warning
| Symptom |
Cause |
Solution |
| Flow had to fetch more than 1000 items from Podio |
Collecting too many items on a date-triggered flow (e.g, using < or > filters) |
Filter only on date field EQUAL to current date; see Throttling Webhooks guidance |
Find Error
| Symptom |
Cause |
Solution |
| Find Error: too many results for SOMETHING (truncating at 99) |
Search returns too many items |
Revise search criteria to reduce results; if using multiple collectors, use Clear Collected to reduce load |
The official version of this content is in English. Some of the Cloud Software Group documentation content is machine translated for your convenience only. Cloud Software Group has no control over machine-translated content, which may contain errors, inaccuracies or unsuitable language. No warranty of any kind, either expressed or implied, is made as to the accuracy, reliability, suitability, or correctness of any translations made from the English original into any other language, or that your Cloud Software Group product or service conforms to any machine translated content, and any warranty provided under the applicable end user license agreement or terms of service, or any other agreement with Cloud Software Group, that the product or service conforms with any documentation shall not apply to the extent that such documentation has been machine translated. Cloud Software Group will not be held responsible for any damage or issues that may arise from using machine-translated content.
DIESER DIENST KANN ÜBERSETZUNGEN ENTHALTEN, DIE VON GOOGLE BEREITGESTELLT WERDEN. GOOGLE LEHNT JEDE AUSDRÜCKLICHE ODER STILLSCHWEIGENDE GEWÄHRLEISTUNG IN BEZUG AUF DIE ÜBERSETZUNGEN AB, EINSCHLIESSLICH JEGLICHER GEWÄHRLEISTUNG DER GENAUIGKEIT, ZUVERLÄSSIGKEIT UND JEGLICHER STILLSCHWEIGENDEN GEWÄHRLEISTUNG DER MARKTGÄNGIGKEIT, DER EIGNUNG FÜR EINEN BESTIMMTEN ZWECK UND DER NICHTVERLETZUNG VON RECHTEN DRITTER.
CE SERVICE PEUT CONTENIR DES TRADUCTIONS FOURNIES PAR GOOGLE. GOOGLE EXCLUT TOUTE GARANTIE RELATIVE AUX TRADUCTIONS, EXPRESSE OU IMPLICITE, Y COMPRIS TOUTE GARANTIE D'EXACTITUDE, DE FIABILITÉ ET TOUTE GARANTIE IMPLICITE DE QUALITÉ MARCHANDE, D'ADÉQUATION À UN USAGE PARTICULIER ET D'ABSENCE DE CONTREFAÇON.
ESTE SERVICIO PUEDE CONTENER TRADUCCIONES CON TECNOLOGÍA DE GOOGLE. GOOGLE RENUNCIA A TODAS LAS GARANTÍAS RELACIONADAS CON LAS TRADUCCIONES, TANTO IMPLÍCITAS COMO EXPLÍCITAS, INCLUIDAS LAS GARANTÍAS DE EXACTITUD, FIABILIDAD Y OTRAS GARANTÍAS IMPLÍCITAS DE COMERCIABILIDAD, IDONEIDAD PARA UN FIN EN PARTICULAR Y AUSENCIA DE INFRACCIÓN DE DERECHOS.
本服务可能包含由 Google 提供技术支持的翻译。Google 对这些翻译内容不做任何明示或暗示的保证，包括对准确性、可靠性的任何保证以及对适销性、特定用途的适用性和非侵权性的任何暗示保证。
このサービスには、Google が提供する翻訳が含まれている可能性があります。Google は翻訳について、明示的か黙示的かを問わず、精度と信頼性に関するあらゆる保証、および商品性、特定目的への適合性、第三者の権利を侵害しないことに関するあらゆる黙示的保証を含め、一切保証しません。
ESTE SERVIÇO PODE CONTER TRADUÇÕES FORNECIDAS PELO GOOGLE. O GOOGLE SE EXIME DE TODAS AS GARANTIAS RELACIONADAS COM AS TRADUÇÕES, EXPRESSAS OU IMPLÍCITAS, INCLUINDO QUALQUER GARANTIA DE PRECISÃO, CONFIABILIDADE E QUALQUER GARANTIA IMPLÍCITA DE COMERCIALIZAÇÃO, ADEQUAÇÃO A UM PROPÓSITO ESPECÍFICO E NÃO INFRAÇÃO.